support-reply
Skill0 starsChanged 47 days agoMITView on GitHub
Draft a support reply that solves the customer's problem in one message, covering how-to, bug, refund, billing and angry emails, following your stated policies, with a clear next step and a note of what to fix so it doesn't recur. Use when answering customer emails, DMs or tickets.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- 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 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
- 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 repository2 other files it gives its agents.
- launch-readinessSkill
- pricing-experimentSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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 20
Find the answer: Search the docs/repo. If you can't confirm it, say what you'll check, not a guess.
- Distinctive: line 39
Never promise dates or features you can't commit to.
- Distinctive: line 40
Never blame the customer. "The instructions weren't clear" beats "you missed step 3".
- Distinctive: line 41
Keep it under 150 words unless steps require more.
“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
When to use
Any customer message that needs an answer. Especially useful for refunds and upset customers, where tone matters most.
Inputs
- The customer's message (and earlier thread if any).
- Your policies: refunds, licence, response times, what you can and can't do.
- Optional: product docs or repo to search for the answer, the customer's order details.
Steps
- Classify: how-to · bug · refund/billing · feature request · complaint · other. Note the one thing they actually need.
- Find the answer. Search the docs/repo. If you can't confirm it, say what you'll check, not a guess.
- Draft, in this order:
- First line: the answer or the action you've taken ("I've refunded your order").
- Steps if needed, numbered, copy-pasteable.
- One line of acknowledgement if they're frustrated. Sincere, not grovelling.
- The next step and when ("If step 2 fails, reply with the error text and I'll look today").
- Policy: apply it as written. If the policy says yes, say yes without making them argue. If it says no, explain once, offer the best alternative, and don't hide behind "policy".
- Internal note: what should change so this question stops arriving (doc fix, bug ticket, FAQ).
Output format
TYPE: ... NEEDS: ...
REPLY:
<ready to send>
INTERNAL: <doc/bug/FAQ action>Rules
- Never promise dates or features you can't commit to.
- Never blame the customer. "The instructions weren't clear" beats "you missed step 3".
- Keep it under 150 words unless steps require more.
Worked example
Input: "I bought the kit yesterday and the workflow fails with 'Could not fetch an OIDC token'. This is useless. I want a refund." Policy: refunds within 14 days, no questions asked.
Output:
TYPE: bug/setup + refund NEEDS: working setup, or their money back
REPLY:
Hi Sam, sorry about that. I've started your refund just in case; it'll show in 5–10 days, and you
can keep the files.
That error has a quick fix if you'd like to keep going. The workflow needs permission to request a
token. Add this under the job in .github/workflows/standup.yml:
permissions:
contents: write
id-token: write
Then re-run it from the Actions tab. If it still fails, reply with the new error line and I'll look
at it today.
INTERNAL: the setup guide doesn't mention id-token: write. Add it to the guide's workflow snippet and
the troubleshooting section, and have setup check for it.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.