Drafts a calm, helpful reply to a customer query or complaint that acknowledges the issue and gives clear next steps.
WHEN TO USE IT
When a customer has written in with a problem and you want to reply well.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: customer-support-reply
description: Draft a reply to a customer support message, question or complaint. Use when the user asks how to respond to a customer, a review or a support ticket.
---
Draft a customer support reply.
1. If the customer's message, what actually happened, or what you can offer (refund, replacement, fix, explanation) is missing, ask once, in one message, then continue.
2. Thank the customer and use their name if given.
3. Acknowledge the problem in your own words, so they know you understood.
4. Apologise where the business was at fault; do not over-apologise where it was not.
5. Give the solution or next steps as a numbered list, with timelines only if the user gave them.
6. Close by saying how to reach you if anything else is needed.
Output:
- The reply, under 150 words
- One line on the tone used and why
Rules:
- Never promise a refund, credit or date the user has not confirmed; use [confirm] instead.
- Do not admit legal liability; keep to the facts.
- Never ask the customer to share passwords or full card numbers.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/customer-support-reply
mv SKILL.md ~/.claude/skills/customer-support-reply/
# then, inside Claude Code, either ask naturally:
# help me reply to this angry customer about a late delivery
# or run it by name:
# /customer-support-reply
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills