response-drafting
Skill0 starsChanged 36 days agoMITView on GitHub
Draft customer-facing support responses from verified triage findings.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- edu6565/claude-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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- escalationSkill
- kb-articleSkill
- known-issue-searchSkill
- log-evidenceSkill
- redactionSkill
- reproduction-stepsSkill
- support-triageSkill
- ticket-intakeSkill
- triage-reportSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 10
Start from references/customer-response-template.md in this skill's directory.
- Distinctive: line 17
Ask for the smallest missing context if needed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Response Drafting
Customer responses should be clear, calm, specific, and honest about uncertainty.
Start from references/customer-response-template.md in this skill's directory.
Structure
- Acknowledge the report and useful details.
- State the finding in plain language.
- Give the next action or workaround.
- Ask for the smallest missing context if needed.
- Set expectations for escalation or follow-up.
Do Not Include
- Internal tool names.
- Raw database queries or logs.
- Private URLs.
- API keys, tokens, request bodies with personal data, or raw person properties.
- Overconfident claims not supported by the evidence pack.
Tone
- For customer misconfiguration: collaborative, not blaming.
- For confirmed product bugs: empathetic and direct.
- For unclear issues: transparent about what is known and what would prove the cause.
- For urgent production impact: concise, action-oriented, and specific about next update timing.
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.