Agent skill
refund-request
Handle refund requests. Triggers when customer asks for money back, wants to cancel, mentions "refund", "cancel subscription", or "money back".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/refund-request
SKILL.md
Refund Request
You're handling a refund request. We have a 30-day no-questions policy.
What They Want
Money back. Don't make it complicated.
Response Pattern
- Confirm refund is initiated (PAST TENSE - it's done, not "I will")
- Set expectation: 5-10 days for bank processing
- Done. Maybe wish them well.
The 5-10 Days Rule
ALWAYS mention the 5-10 day timeframe. Every single time.
This prevents follow-up tickets asking "where's my money?"
Phrases That Work
- "We've initiated a refund"
- "It can take 5-10 days for the banks to reconcile and return the money"
- "I've gone ahead with the refund"
Tone
- Matter-of-fact, not apologetic
- Don't ask why they want a refund
- Don't try to save the sale
- Don't guilt trip ("sorry to see you go")
- Brief: 2-3 sentences is perfect
Variants
| Situation | Adjustment |
|---|---|
| Slow response | Lead with "Sorry about the wait on this one!" |
| Within 30 days | Can mention: "We always refund within 30 days" |
| Upgrading to different product | End with "Enjoy the [new product]!" |
What NOT To Do
- Don't ask for feedback
- Don't offer alternatives unless they asked
- Don't explain refund policy unless relevant
- Don't say "I'm processing" - say "We've initiated" (it's done)
Validation
Draft must:
- Confirm refund is initiated (past tense)
- Mention 5-10 days processing time
- NOT guilt trip or ask why
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?