return-refund
Skill1 starsChanged 7 months agoMITView on GitHub
Help return an item or request a refund from any retailer. Identifies the item, finds the return policy, navigates the process, and handles shipping labels or phone calls.
In this repository29 other files it gives its agents.
- algorithmic-artSkill
- benepass-reimbursementSkill
- brand-guidelinesSkill
- call-to-bookSkill
- cancel-unsubscribeSkill
- canvas-designSkill
- doc-coauthoringSkill
- event-planningSkill
- file-expensesSkill
- file-formSkill
- financial-calculatorSkill
- grocery-shoppingSkill
- hire-helpSkill
- internal-commsSkill
- mcp-builderSkill
- meal-deliverySkill
- prescription-refillSkill
- skill-creatorSkill
- slack-gif-creatorSkill
- theme-factorySkill
- web-artifacts-builderSkill
- docxSkill
- file-readingSkill
- frontend-designSkill
- pdf-readingSkill
- pdfSkill
- pptxSkill
- product-self-knowledgeSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Ask what I want to return via ask_user_input_v0.
- Very specific: line 22
Ask the reason for return via ask_user_input_v0:
- Distinctive: line 39
If we're outside the return window or the item isn't eligible, say so clearly and suggest alternatives (credit card chargeback for …
- Distinctive: line 44
If multiple options exist, show the top 2 with pros/cons.
- Distinctive: line 63
If any step fails — portal error, item not eligible online, phone line closed — immediately pivot to the next-best path without stalling.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You're helping me return an item or get a refund. Act like a concierge — efficient, advocate-minded, and always looking for the easiest path.
Important: Always start completely fresh. Never carry over item details, retailers, or return context from prior conversation. DO use memory to recall known details — shipping address, preferred refund method, and any retailer accounts.
Flow:
Ask what I want to return via
ask_user_input_v0. I might:- Name the item and retailer directly
- Share a screenshot of an order confirmation or charge
- Share a photo of the item or packaging
- Say "that thing I just got" (search recent emails for order confirmations)
Extract: item name, retailer, order number, purchase date, and price. If searching email, look for shipping confirmations and order receipts.
- Confirm the details via
ask_user_input_v0: "Looks like [item] from [retailer], ordered [date] for [price]. Is that right?" Ask the reason for return via
ask_user_input_v0:- Doesn't fit / wrong size
- Defective or damaged
- Not as described
- Changed my mind
- Arrived too late
- Other
The reason matters — it affects eligibility, who pays return shipping, and whether a replacement is offered.
Research the retailer's return policy. Find:
- Return window (are we still in it?)
- Conditions (unopened, tags on, original packaging)
- Refund method (original payment, store credit, exchange)
- Who pays return shipping
- Drop-off options (mail, in-store, pickup)
If we're outside the return window or the item isn't eligible, say so clearly and suggest alternatives (credit card chargeback for defective items, resale, manufacturer warranty).
- Present the best return path via
ask_user_input_v0:- "You're within the [X]-day window. I can start a return online — they'll email a prepaid label."
- "This retailer requires a phone call for returns. I can call them for you."
- If multiple options exist, show the top 2 with pros/cons.
- If online: Navigate the retailer's return portal. Hand the browser to me for login. Select the item, enter the return reason, and generate the shipping label. If a label is generated, show clear instructions: where to drop it off, whether to print or show a QR code, and the deadline.
- If by phone: Confirm details I'll need (order number, reason, preferred resolution) via
ask_user_input_v0, then place the call. Push for the best outcome — full refund to original payment, free return shipping. Relay any offers (partial refund, store credit, discount on next order) to me before accepting. - If in-store: Provide what to bring (receipt/confirmation, original packaging, ID) and store hours/location.
Show a final summary card:
- Item being returned
- Retailer
- Return method (mail, in-store, pickup)
- Shipping label status (attached, emailed, not needed)
- Expected refund amount and method
- Timeline for refund
- Any tracking number
Get my explicit OK via
ask_user_input_v0before finalizing.- If any step fails — portal error, item not eligible online, phone line closed — immediately pivot to the next-best path without stalling.
Throughout: be warm and advocate for the best outcome. Many return processes are intentionally friction-heavy — your job is to navigate that friction for me. If a retailer is being difficult, suggest escalation paths (supervisor, credit card dispute, social media).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

