NZ Post Tracking & Returns Helper
v1.0.0low riskTracks NZ Post / CourierPost parcels from your tracking numbers and drafts returns labels and missing-parcel claims.
Install
Claude Code (CLI)(min >=1.0.0)
download โ# Per-user (recommended) โ overwrites any existing skill of this name:
curl -fsSL https://localskills.ai/api/install/claude-code/nz/nz-post-tracking-helper -o /tmp/nz-post-tracking-helper.zip \
&& unzip -o /tmp/nz-post-tracking-helper.zip -d ~/.claude/skills/ \
&& rm /tmp/nz-post-tracking-helper.zipInstalls to ~/.claude/skills/<slug>/
Cursor(min >=0.40.0)
download โ# From your project root:
mkdir -p .cursor/rules \
&& curl -fsSL https://localskills.ai/api/install/cursor/nz/nz-post-tracking-helper -o .cursor/rules/nz-post-tracking-helper.mdcInstalls to .cursor/rules/<slug>.mdc
Codex CLI(min >=1.0.0)
download โ# Codex's skill format is still settling โ drop the folder where your
# Codex installation looks for skills (typically .codex/skills/):
curl -fsSL https://localskills.ai/api/install/codex/nz/nz-post-tracking-helper -o /tmp/nz-post-tracking-helper.zip \
&& unzip -o /tmp/nz-post-tracking-helper.zip -d ./ \
&& rm /tmp/nz-post-tracking-helper.zipInstalls to .codex/skills/<slug>/
README
NZ Post Tracking & Returns Helper
You feed the skill tracking numbers and screenshots of confirmation emails. It produces a clean parcel status board and drafts the messages you need when something goes wrong.
What it does
- Takes tracking numbers (NZ Post / CourierPost / Pace) and pasted status screenshots and keeps a tidy "what's in transit" view.
- Drafts the wording for a missing-parcel claim through NZ Post's online claim form when something hasn't moved in too long.
- Drafts the wording for a returns shipment to the original sender โ including consumer-rights references where relevant.
- Calculates the realistic delivery window for a given service tier (Economy vs Tracked vs CourierPost overnight).
It does NOT scrape NZ Post's tracking page. You give it the status text or screenshot; the skill structures it.
Why this is useful
NZ Post's tracking emails are good. The website is fine. What's painful is:
- Tracking 6 parcels at once from different retailers (e.g. before Christmas).
- Knowing when "your parcel is at the depot" has crossed from normal to "I should ask".
- Writing the missing-parcel email so it doesn't disappear into a queue.
- Drafting a returns label / message under the Consumer Guarantees Act when the item isn't fit for purpose.
Inputs
- Tracking numbers (any format:
NZ-prefix,CPfor CourierPost, etc.). - Screenshots or pasted text of the carrier's status page.
- The retailer (helps the skill know which return policy to reference).
- Order date and expected delivery date if you have them.
Outputs
A status board:
Active parcels (3)
------------------
NZ123456789NZ Mighty Ape Out for delivery 2026-05-18
CP987654321 Allbirds Awaiting collection Auckland depot
NZ555444333NZ Trade Me Delayed (5 days) โ flagged
Flagged for action:
- NZ555444333NZ has been "delayed" for 5 days. Realistic for Economy
is up to 7 working days; this is at day 5. Wait 2 more, then file.
A drafted message when needed:
DRAFT โ Missing parcel inquiry, NZ Post claims form
---------------------------------------------------
Tracking: NZ555444333NZ
Sent: 2026-05-08 from <SENDER>
Service: Economy Tracked
Last status: "In transit" (2026-05-11)
The parcel hasn't moved in 7 working days. Could you confirm its
current location and expected delivery date? If it's been lost in
transit, please open a claim under your missing-parcel process.
<NAME>
<DAYTIME PHONE>
Permissions
fileSystem.read:downloadsโ for screenshots and PDFs you've saved.fileSystem.write:outputsโ to save the tracking history JSON.- No network. The skill never contacts NZ Post.
- No shell.
Tone
Polite. Factual. NZ-direct. The skill writes claims that customer service can act on โ no threats, no escalation, no "what's the point of paying for tracked ifโฆ".
What it won't do
- Auto-poll NZ Post's tracking page. NZ Post's terms forbid scraping; we comply.
- Generate a label. NZ Post labels require account integration and prepaid postage.
- File a claim on your behalf. You submit through the NZ Post claims portal.
- Determine whether something is genuinely lost. The skill flags items that look stuck; the carrier decides.
Author
Paul Grey at Second Brain NZ.
Version
1.0.0 โ initial release.
Skill instructions (SKILL.md)
View the prompt the agent receives
NZ Post Tracking & Returns Helper โ SKILL
You maintain a tidy view of the user's in-flight parcels and draft the messages they need when something goes wrong. You don't contact NZ Post directly. You don't auto-track.
Operating rules
- You never scrape, poll, or contact NZ Post / CourierPost / any carrier API. All status comes from the user pasting it in or providing screenshots.
- You don't speculate. If a parcel's status hasn't changed, you say so; you don't invent reasons.
- Realistic delivery windows (NZ working days, excluding Saturdays unless service includes Saturday delivery):
- Economy / Tracked (NZ Post): 2โ7 working days nationwide.
- CourierPost Overnight: next working day to most NZ destinations, +1 for rural.
- CourierPost National (3โ4 day): 3โ4 working days.
- Pace / 1โday pickup: as quoted on the sender's confirmation.
- International incoming: highly variable; don't predict.
- Flag thresholds:
- Economy parcel: flag at day 8 (one day past the upper end).
- CourierPost Overnight: flag at day 3 (over-the-top late).
- International: flag only on user request.
- Output two blocks: status board and (when needed) drafted message. The user copies and acts.
Inputs you accept
- Tracking number (any carrier format).
- Carrier service tier (Economy / Tracked / CourierPost Overnight / Pace / International).
- Last known status (pasted or screenshot).
- Sender / retailer name.
- Sent date and expected delivery date.
Storage
Keep a JSON file (~/Documents/nz-post-tracking.json by default):
{
"parcels": [
{
"tracking": "NZ123456789NZ",
"carrier": "NZ Post",
"service": "Economy Tracked",
"sender": "Mighty Ape",
"sent": "2026-05-08",
"expected_by": "2026-05-15",
"status_log": [
{ "date": "2026-05-08", "text": "Accepted" },
{ "date": "2026-05-11", "text": "In transit" }
]
}
]
}
Append; don't overwrite.
Status board format
Active parcels (<N>)
--------------------
<TRACKING> <SENDER> <SHORT STATUS> <DETAIL>
...
Flagged for action:
- <TRACKING>: <reason>
Short status options (pick the closest to the carrier's wording):
Acceptedโ at sender / awaiting pickupIn transitโ movingAt depotโ sitting in a sorting facilityOut for deliveryโ on the truck todayDeliveredโ doneCard to callโ user wasn't home, paper card leftReturned to senderโ couldn't deliver, bouncing backDelayedโ carrier marked it delayedLostโ carrier confirmed lost (only if explicit)
Missing-parcel claim format
Use only when the parcel is past the flag threshold:
DRAFT โ Missing parcel inquiry, NZ Post claims form
---------------------------------------------------
Tracking: <TRACKING>
Sent: <YYYY-MM-DD> from <SENDER>
Service: <SERVICE TIER>
Last status: <last known> (<date>)
The parcel hasn't moved in <N> working days, past the typical delivery
window for this service. Could you confirm its current location and
expected delivery date? If it's been lost in transit, please open a
claim under your missing-parcel process and let me know what's needed
from my end.
<NAME>
<DAYTIME PHONE>
After the draft, output the carrier's process:
What to do next
---------------
1. Open https://www.nzpost.co.nz/help-support/claim-a-refund-or-loss
2. Pick "Missing items".
3. Enter the tracking number.
4. Paste the above as your description.
5. Attach: order confirmation if you have it.
6. Submit and keep the reference number โ you'll need it for the
retailer's refund process (under the Consumer Guarantees Act,
delivery is the retailer's responsibility, not yours).
Returns-to-sender format
For a return under the CGA (faulty / not-as-described):
DRAFT โ Return request, post to <SENDER>
----------------------------------------
Original order: <ORDER NUMBER>, placed <YYYY-MM-DD>, received <YYYY-MM-DD>
Returning the following items under the Consumer Guarantees Act 1993
(section <6 โ acceptable quality / 9 โ description>):
- <ITEM> โ <one-line reason>
Could you confirm:
1. Whether you want the item returned, photo evidence, or both.
2. The return shipping address and whether you'll cover the return
postage (under s 18(2) the retailer covers reasonable costs of
returning faulty goods).
Thanks,
<NAME>
After the draft:
What to do next
---------------
1. Email <SENDER>'s customer service email or open a chat.
2. Paste the draft.
3. Wait for them to confirm return method before posting anything.
4. Use a tracked service for the return โ get the receipt.
What you will not do
- Auto-poll any tracking page.
- Print or generate a shipping label.
- Decide whether a parcel is "lost" โ only the carrier can declare that.
- Threaten the carrier or retailer. Wrong tone, slows resolution.
- Help with international customs disputes (out of scope; refer to NZ Customs).
Tone
NZ-polite. Factual. The carriers and retailers respond well to dates, tracking numbers, and the right statutory reference. Skip the venting.
Self-check
- Is the flag threshold met before drafting a missing-parcel inquiry?
- Is the right CGA section quoted for a return?
- Have I appended to the history, not overwritten?
- No invented status text or dates?
If any answer is "no", fix it.
Changelog
Changelog
[1.0.0] โ 2026-05-20
Added
- Initial release.
- Status-board view of in-flight parcels with per-service realistic delivery windows.
- Drafts NZ Post claims-portal inquiries and CGA-aware returns messages.
- Flag thresholds tuned per service tier (Economy/CourierPost/Pace).
- Zero network permissions โ never contacts NZ Post.