logistics-tracking_skill

Overview

This skill tracks international packages by tracking number across 3100+ carriers via 17track. It returns shipment status, current location, event timeline, and delivery estimates. Optionally use TRACK17_API_KEY for the official API; without a key it falls back to a headless browser query.

How this skill works

The skill queries 17track to detect carrier and fetch tracking events. With TRACK17_API_KEY it calls the official API for reliable, wide-coverage results. Without a key it runs a headless Playwright query as a fallback. Tools available include single-package tracking, carrier detection, batch tracking (up to 40), and human-readable status explanations.

When to use it

• User asks “where is my package” or provides a tracking number
• Check shipment status, expected delivery time, or event timeline
• Investigate customs clearance, exceptions, or delivery failures
• Track multiple packages efficiently with batch queries
• Auto-detect carrier when the user is unsure of provider

Best practices

• Set TRACK17_API_KEY for the most reliable results and full carrier coverage
• Wait 24–48 hours after shipment before querying for best data availability
• Allow ~2 hours between repeated queries for the same number to avoid rate limiting
• Install Playwright if running without an API key to enable the browser fallback
• Use batch_track for lists of packages to reduce repeated calls and speed up results

Example use cases

• Track a single package: provide tracking number to get status, location, and timeline
• Identify carrier when you only have the tracking code format
• Batch-check 10–40 orders for a daily fulfillment update
• Explain a status code like CustomsClearance or Exception to tell the user next steps
• Deploy as an HTTP service so end users can query tracking without holding an API key