parcel-tracking

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill parcel-tracking
0 commentsdiscussion
summary

Find tracking numbers from Gmail dispatch emails and check delivery status for Australian and international couriers.

skill.md

Parcel Tracking

Find tracking numbers from Gmail dispatch emails and check delivery status for Australian and international couriers.

When to Use

  • "Where's my parcel / package / order?"
  • "Has my [product] arrived / shipped yet?"
  • "Track my order from [store]"
  • "What's the status of my delivery?"
  • "Do I have a tracking number for [item]?"
  • User pastes or mentions a tracking number
  • "Check the StarTrack / AusPost / Aramex / Toll tracking"

Workflow

Step 1: Find the Tracking Number

If the user already provided a tracking number, skip to Step 2.

Otherwise, search Gmail for dispatch emails. Look for recent messages matching:

dispatched OR shipped OR "tracking number" OR "consignment number" newer_than:30d

For a specific store or order, narrow the search:

from:mwave.com.au dispatched
from:amazon.com.au shipped

Read the email body and extract:

  • Tracking / consignment number
  • Carrier name
  • Order number
  • Dispatch date
  • Delivery notes (signature required, etc.)

Gmail access: Use whatever Gmail tool is available (Gmail MCP, gws CLI gws gmail, or ask the user to check manually and paste the tracking number).

Step 2: Identify the Carrier and Build the Tracking Link

Use the table below to identify the carrier from the tracking number format or dispatch email, then build the direct tracking link where possible.

Carrier Number format / example Direct tracking link
AusPost / StarTrack Alphanumeric, e.g. 36VJ65064757, JD123456789AU https://auspost.com.au/mypost/track/details/{NUMBER}
Sendle 6-8 alphanumeric chars, e.g. SNFJJ3 https://track.sendle.com/tracking?ref={NUMBER}
DHL 10-12 digits, e.g. 1234567890 https://www.dhl.com/au-en/home/tracking.html?tracking-id={NUMBER}
FedEx 12-15 digits, or AU+10 digits https://www.fedex.com/apps/fedextrack/?tracknumbers={NUMBER}
TNT (now FedEx) 9 digits, e.g. 907384999 https://www.tnt.com/express/en_au/site/shipping-tools/tracking.html (paste)
UPS Starts with 1Z, 18 chars https://www.ups.com/track?tracknum={NUMBER}
Aramex (formerly Fastway) Numeric label number, varies https://www.aramex.com.au/tools/track (paste)
CouriersPlease Numeric or CP prefix https://www.couriersplease.com.au/tools-track (paste)
Toll / MyToll Numeric consignment, varies https://mytoll.com/ (paste)
Team Global Express Numeric, varies https://myteamge.com/ (paste)
Hunter Express Alphanumeric, e.g. AIM478695 https://www.hunterexpress.com.au/tracking/ (paste)
Border Express Numeric, varies https://www.borderexpress.com.au/tracking/ (paste)
Direct Freight Express Numeric consignment https://www.directfreight.com.au/ConsignmentStatus.aspx (paste)

Deep-links (tracking number in URL): AusPost/StarTrack, Sendle, DHL, FedEx, UPS.

Form-based (provide link + number separately): Aramex, CouriersPlease, Toll, Team Global Express, Hunter Express, Border Express, Direct Freight Express, TNT.

If carrier is unknown: Default to AusPost (most common in Australia), or ask the user to check their dispatch email.

Step 3: Try to Get Live Status

If web scraping tools are available, try scraping the tracking page:

url: {direct tracking URL}
wait_for: 3000 (many tracking pages are JS-rendered)

Many tracking pages return limited data when scraped. AusPost is particularly JS-heavy. If scraping returns useful status info, include it. If not, just provide the direct link. Don't mention failed scrapes to the user.

If browser automation is available (Chrome MCP, Playwright), navigate to the tracking page and read the status directly.

If no scraping/browser tools are available, skip this step and provide the link.

Step 4: Present Results

Always include:

  1. Current status (from scrape if available, or from dispatch email)
  2. Direct tracking link (always)
  3. Expected delivery window (if known)
  4. Delivery notes (signature required, card-to-collect, etc.)

Example: Carrier with Deep Link

Order IN03069870 — Mac mini x 2
Dispatched by Mwave via AusPost/StarTrack on 17 Mar

Tracking: 36VJ65064757
Status: In transit — processed at Sydney sorting facility
Expected: Thu 19 – Fri 20 Mar
Note: Signature required. If no one home, parcel goes to local post office.

Track live: https://auspost.com.au/mypost/track/details/36VJ65064757

Example: Form-Based Carrier

Order 12345 — [item]
Dispatched via Toll on 15 Mar

Consignment: TXY9876543
Expected: 3-5 business days

Track at: https://mytoll.com/
Paste consignment number: TXY9876543

Handling Multiple Parcels

Search broadly:

(dispatched OR shipped OR "on its way" OR "tracking number") newer_than:30d

Present each parcel as a separate block.

Carrier Contact Numbers (Australia)

Carrier Phone Hours (AEST/AEDT)
AusPost / StarTrack eParcel 13 13 18 Mon-Fri 8am-6pm
StarTrack (account customers) 13 23 45 Business hours
CouriersPlease 13 00 36 16 Business hours
Toll Priority 13 15 31 Mon-Fri 7am-10pm, Sat-Sun 7am-5pm
Toll IPEC 1300 865 547 Business hours
Hunter Express 02 9780 4099 Business hours
DHL 13 14 06 Business hours
FedEx / TNT 13 26 10 Business hours
UPS 13 26 77 Business hours
Aramex See aramex.com.au/contact-us Business hours
Sendle Online only (support form)
Team Global Express myteamge.com contact form

Carrier-Specific Notes

AusPost / StarTrack

  • URL format: https://auspost.com.au/mypost/track/details/{TRACKING_NUMBER} — tracking number goes directly in the path
  • Sparse tracking events after Sydney (Lidcombe/Chullora) processing is normal for regional deliveries
  • Allow up to 24 hours after dispatch for tracking to appear
  • Signature-required parcels go to local post office if undelivered

Sendle

  • Sendle halted all parcel pick-ups in early 2025 and directed customers to Aramex. Existing Sendle shipments still trackable.
  • Deep link: https://track.sendle.com/tracking?ref={SENDLE_REFERENCE}

Toll vs Team Global Express

  • Toll Global Express was sold and rebranded as Team Global Express — different tracking system
  • Domestic Toll parcels (IPEC, Priority, Express) still use MyToll

Tool Flexibility

This skill works with whatever tools are available:

Tool What it enables
Gmail access (any MCP or CLI) Search dispatch emails for tracking numbers
Web scraper (any MCP) Attempt live status from tracking pages
Browser automation (Chrome MCP, Playwright) Navigate tracking pages for JS-rendered status
None of the above User provides tracking number, skill provides the correct link
how to use parcel-tracking

How to use parcel-tracking on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add parcel-tracking
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill parcel-tracking

The skills CLI fetches parcel-tracking from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/parcel-tracking

Reload or restart Cursor to activate parcel-tracking. Access the skill through slash commands (e.g., /parcel-tracking) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.739 reviews
  • Ava Jackson· Dec 20, 2024

    We added parcel-tracking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Dec 16, 2024

    Keeps context tight: parcel-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Soo Flores· Dec 16, 2024

    Registry listing for parcel-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Naina Thompson· Dec 8, 2024

    parcel-tracking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Naina Brown· Nov 27, 2024

    parcel-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sakshi Patil· Nov 7, 2024

    Registry listing for parcel-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Liu· Nov 7, 2024

    Keeps context tight: parcel-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chaitanya Patil· Oct 26, 2024

    parcel-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Omar Abbas· Oct 26, 2024

    parcel-tracking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Advait Desai· Oct 18, 2024

    Registry listing for parcel-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 39

1 / 4