support-reply
Skill0 starsChanged 3 months agoMITView on GitHub
Draft an on-brand customer support reply. Use when someone pastes a customer message or ticket and needs a helpful, correct response that solves the problem and keeps the customer happy.
5 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
- solvio-dev/sample-business-skillstheir own version, first seen Jul 28, 2026
- charanjit-singh/lovable-skillstheir own version, first seen May 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- 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
- 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 repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- contract-summarizerSkill
- crm-note-cleanerSkill
- data-cleanerSkill
- expense-summarySkill
- faq-builderSkill
- follow-up-emailSkill
- invoice-builderSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- review-responderSkill
- social-post-packSkill
- sop-writerSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If solving it needs a fact you don't have (refund policy, account detail), ask for it rather than guessing.
- Distinctive: line 19
If you can't fully resolve it, say what you're doing next and when they'll hear back.
- Distinctive: line 28
Never invent a policy or a promise.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Support Reply
A reply that actually solves it and leaves the customer feeling looked after.
Inputs needed
- The customer's message or ticket.
- (Optional) Relevant facts: account status, policy, known fix, or product docs.
If solving it needs a fact you don't have (refund policy, account detail), ask for it rather than guessing.
Steps
- Acknowledge the specific problem so the customer feels heard.
- Give the answer or fix in clear steps.
- If you can't fully resolve it, say what you're doing next and when they'll hear back.
- Set correct expectations. Never promise what policy doesn't allow.
- Close warmly and invite a follow-up.
Output format
A ready-to-send reply. For anything sensitive (refunds, complaints, outages), add a one-line note flagging what a human should confirm before sending.
Voice & rules
- Empathy first, then the fix.
- Never invent a policy or a promise. Flag unknowns.
- Match the customer's tone: brief for brief, warmer for upset.
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.