support-reply
Skill0 starsChanged 6 days agoMITView on GitHub
Draft a reply to a customer support message, ticket, review or chat. Use when the user pastes a customer message and asks how to respond, "answer this ticket", "reply to this complaint", or wants a support macro or template.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- leymish01-oss/claude-code-founder-skills-sampletheir own version, first seen Oct 20, 2026
- munnam77/claude-for-solopreneurstheir own version, first seen Oct 20, 2026
- localoy-ai/localstacktheir own version, first seen Oct 2, 2026
- nawazxz/20-claude-skills-for-businesstheir own version, first seen Aug 12, 2026
- solvio-dev/sample-business-skillstheir own version, first seen Jul 28, 2026
- charanjit-singh/lovable-skillstheir own version, first seen May 22, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- charanjit-singh/lovable-skills★ 10same name
- localoy-ai/localstack★ 2same name
- leymish01-oss/claude-code-founder-skills-sample★ 0same name
- munnam77/claude-for-solopreneurs★ 0same name
- nawazxz/20-claude-skills-for-business★ 0same name
- solvio-dev/sample-business-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- api-docsSkill
- changelogSkill
- ci-failure-fixSkill
- code-reviewSkill
- commit-messageSkill
- competitor-analysisSkill
- data-analystSkill
- debug-detectiveSkill
- dependency-upgradeSkill
- dockerizeSkill
- email-replierSkill
- eval-promptSkill
- incident-postmortemSkill
- meeting-notesSkill
- migration-safetySkill
- pr-descriptionSkill
- product-specSkill
- readme-writerSkill
- refactor-safelySkill
- research-briefSkill
- security-checkSkill
- seo-articleSkill
- sql-helperSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read the policy, FAQ, docs or macros available in the project or conversation (refunds, shipping, SLAs, warranty).
- Distinctive: line 28
If information is missing (order number, email, screenshot, device), ask for all of it in one list.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customer support reply
1. Triage
- What does the customer want (refund, fix, information, to be heard)? List every issue if there are several.
- Type: bug, how-to question, billing, shipping/delivery, account access, feature request, complaint.
- Mood: calm, frustrated, angry, threatening to leave.
2. Escalate instead of answering alone when the message involves
legal threats or lawyers, chargebacks or fraud, safety or injury, a security vulnerability or account compromise, data deletion/access requests (GDPR, CCPA), press or public social media posts, or a refund/credit above what the policy lets you grant. Then draft a short holding reply (received, who will follow up, when if known) and an internal note saying why it needs a human.
3. Check the source of truth
Read the policy, FAQ, docs or macros available in the project or conversation (refunds, shipping, SLAs, warranty). If none are available, write the reply with [policy: ...] placeholders. Never:
- promise anything the policy does not allow
- invent timelines ("within 24 hours") without a stated SLA
- state account facts you cannot see (order status, tracking, plan) -> use
[order status] - say an action is done ("I've issued a refund") unless the user told you it is done. Write "I've requested..." or
[confirm refund issued].
4. Draft
- First sentence names their specific problem, not "we apologize for any inconvenience". Apologise once if we are at fault; do not admit fault for things not yet confirmed.
- The answer or fix. Steps as a numbered list, one action per step, using the exact names of buttons and menus from the docs.
- What happens next and who acts: "You'll get an email from us when...".
- If information is missing (order number, email, screenshot, device), ask for all of it in one list.
- Under 120 words unless steps require more. Customer's language. No internal jargon or ticket codes. Never blame the customer.
- Sign with
[Agent name].
5. Internal note (separate, only if useful)
Bug to report (steps, frequency), doc gap, policy exception requested, or churn risk.
Output
- Triage line: type, mood, escalate yes/no.
- The reply.
- Placeholders to fill.
- Internal note, if any.
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.