support-reply
Skill10 starsChanged 6 months agoMITView on GitHub
Use when drafting customer support replies, help desk responses, or empathetic responses to user issues from tickets or message paste-ins. Not for in-app UI copy or legal policy documents.
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
- 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
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- 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 repository56 other files it gives its agents.
- accessibility-passSkill
- analytics-eventsSkill
- api-error-handlingSkill
- audit-logging-backendSkill
- background-jobs-and-cronSkill
- dark-mode-and-themingSkill
- dashboard-charts-rechartsSkill
- edge-functions-and-webhooksSkill
- email-and-notificationsSkill
- error-states-and-empty-uiSkill
- feature-flags-and-togglesSkill
- file-upload-storageSkill
- i18n-multi-languageSkill
- lovable-prompting-playbookSkill
- lovable-ship-checklistSkill
- migration-playbookSkill
- multi-tenant-backendSkill
- onboarding-copySkill
- optimistic-updatesSkill
- payment-failed-and-recoverySkill
- payment-webhook-idempotencySkill
- payment-webhook-testingSkill
- performance-budgetSkill
- pg-cron-recipesSkill
- pg-cron-scheduled-jobsSkill
- pg-cron-with-pg-net-edgeSkill
- postgres-full-text-searchSkill
- postgres-triggers-and-functionsSkill
- pricing-and-billingSkill
- programmatic-seo-content-qualitySkill
- programmatic-seo-pagesSkill
- rate-limiting-edgeSkill
- realtime-and-subscriptionsSkill
- refactor-safe-diffSkill
- release-notesSkill
- seo-core-web-vitalsSkill
- seo-landing-pageSkill
- seo-meta-tags-spaSkill
- seo-sitemap-generationSkill
- seo-ssr-and-prerenderingSkill
- seo-structured-dataSkill
- server-input-validationSkill
- shadcn-patternsSkill
- soft-delete-and-archivingSkill
- stripe-one-time-payment-webhooksSkill
- stripe-payment-webhooksSkill
- supabase-auth-flowsSkill
- supabase-database-designSkill
- supabase-rls-and-authSkill
- tanstack-infinite-queriesSkill
- tanstack-mutations-and-invalidationSkill
- tanstack-prefetch-and-hydrationSkill
- tanstack-query-alternativeSkill
- tanstack-router-data-loadersSkill
- tanstack-start-server-routesSkill
- typed-api-hooks-formsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
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 26
Ask one focused question; do not bombard with ten questions.
- Distinctive: line 30
If billing, data loss, or security: note internal escalation path.
“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
Tone
- Professional, warm, concise.
- Acknowledge frustration without over-apologizing.
- Second person ("you") — avoid blame.
Structure
- Acknowledge the issue in one sentence.
- Answer / fix steps numbered if procedural.
- Next step — what you need from them OR what happens next.
- Close — offer follow-up; no guilt trips.
When info is missing
Ask one focused question; do not bombard with ten questions.
Escalation
If billing, data loss, or security: note internal escalation path; do not promise refunds not in policy.
Avoid
- Jargon without explanation.
- "As per my last email" tone.
- Sharing other customers' data.
- Making up refund/credit policy — use placeholders
[confirm with billing policy].
Output format
Ready to paste email/chat; subject line if email.
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.