Shipping Skill: Handle Delivery Issues Without Guesswork

Where this fits

A customer opens a chat: "Where is my package? It was supposed to arrive three days ago." Without a clear protocol, your agent either guesses or escalates. The shipping skill encodes the exact rules for delivery estimates, lost parcels, and address changes, so your agent gives consistent, accurate answers without manual intervention.

Why agents benefit

• Forces agents to request a tracking number first, eliminating guesswork and ambiguous responses.
• Defines "lost" as 10 business days past the estimated delivery date, preventing premature claims and false promises.
• Provides conditional logic for address changes based on parcel location (origin depot vs. in transit).
• Gives clear instructions for handling delays: say "delayed" and offer to re-check tomorrow.
• Reduces support escalations by giving agents a decision tree they can follow autonomously.

Practical scenarios

Delayed package inquiry

The customer provides a tracking number. The agent checks the current status and sees the estimated delivery date was yesterday. Per the skill, the agent states the parcel is delayed and offers to re-check tomorrow, avoiding the word "lost" and setting correct expectations.

Lost parcel claim after 10 business days

A customer reports a missing package. The agent first checks the tracking number and the estimated delivery date. If it has been more than 10 business days past that date, the agent can treat it as lost and initiate the appropriate refund or replacement process. Otherwise, it follows the delay protocol.

Address change while parcel is at origin depot

The customer needs to update the delivery address. The agent checks the parcel's location. If it's still at the origin depot, the agent can process the change. If it has left, the agent explains that the customer must refuse delivery and place a new order, using the skill's rule to avoid incorrect promises.

Add it to your agent workflow

Install the skill with:

npx skills add footprintjs/agentfootprint --skill shipping

Once installed, you can load the skill into your agent's context. For example, when a shipping query is detected, your agent can invoke the skill's logic:

const shipping = require('shipping');
const response = shipping.handleQuery({ trackingNumber, userQuery });

The skill provides the rules and response templates, so your agent can generate accurate replies without hardcoding shipping policies.

Compare before adopting

Before integrating, compare this skill against your existing shipping logic or other available skills. Check its maintenance freshness (last commit, issue responses), community signals (20 stars, but is it actively used?), and whether it covers your specific carrier or region. Also consider if your workflow already has equivalent rules—this skill is most valuable when you need a quick, battle-tested starting point.

Why it is worth tracking

The skill has a clear, focused scope and a well-defined rule set, which makes it easy to test and trust. With 20 stars and an active repository from footprintjs, it shows early community interest. If you handle shipping queries frequently, this skill can save you from reinventing common logic. Keep an eye on its update frequency and community feedback—if it gains traction, it may become a standard component for customer support agents. You can find more details and usage examples on the OpenAgentSkill listing to see how it fits into the broader agent ecosystem.