track17 (17TRACK parcel tracking)
This skill lets Clawdbot keep a local list of your parcels, track their state via the
17TRACK Tracking API v2.2
, and summarise changes.
It stores everything in a small
SQLite DB
under your
workspace
(by default:
or
python3 { baseDir } /scripts/track17.py status "RR123456789CN" Webhooks (optional) 17TRACK can push updates to a webhook URL. This skill supports webhook ingestion in two ways: A) Run the included webhook server python3 { baseDir } /scripts/track17.py webhook-server --bind 127.0 .0.1 --port 8789 Then point 17TRACK's webhook URL at that server (ideally via a reverse proxy or Tailscale Funnel). B) Ingest webhook payloads from stdin/file cat payload.json | python3 { baseDir } /scripts/track17.py ingest-webhook
or
python3 { baseDir } /scripts/track17.py ingest-webhook --file payload.json If you saved webhook deliveries to the inbox directory, process them: python3 { baseDir } /scripts/track17.py process-inbox Common actions Stop tracking: python3 { baseDir } /scripts/track17.py stop 1 Retrack a stopped parcel: python3 { baseDir } /scripts/track17.py retrack 1 Delete a parcel from local DB (does not delete at 17TRACK unless you also call delete-remote ): python3 { baseDir } /scripts/track17.py remove 1 Show API quota: python3 { baseDir } /scripts/track17.py quota Operating guidance for the agent Prefer sync (polling) for simplicity unless the user explicitly wants webhooks. After adding a package, run status once to confirm a valid carrier/status was returned. When summarising, prioritise: delivered/out for delivery exception/failed delivery customs holds carrier handoffs Never echo TRACK17_TOKEN or TRACK17_WEBHOOK_SECRET .