customer-success
Skill1 starsChanged 8 months agoMITView on GitHub
Customer success skill — support triage, health scoring, churn prediction, onboarding. Use when tasks involve customers, support tickets, NPS, churn, or renewals.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- zime-ai/zime-gtm-skillstheir own version, first seen Nov 1, 2026
- productionx-in/Core-Skillstheir own version, first seen Sep 29, 2026
- donatassimkus/claude-ai-skillstheir own version, first seen Jul 23, 2026
- samuelcastro/startup-skillstheir own version, first seen Jun 10, 2026
- sohaibdevv/Claude-Agentic-Skills2.0-versiontheir own version, first seen Jun 9, 2026
- vignesh2027/Claude-Agentic-Skills2.0-versiontheir own version, first seen May 20, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- claude-office-skills/skills★ 433same name
- getnao/sylph★ 195same name
- travisjneuman/.claude★ 106same name
- zime-ai/zime-gtm-skills★ 19same name
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6same name
- sohaibdevv/Claude-Agentic-Skills2.0-version★ 2same name
- donatassimkus/claude-ai-skills★ 1same name
- productionx-in/Core-Skills★ 1same name
- samuelcastro/startup-skills★ 1same 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 repository13 other files it gives its agents.
- financeSkill
- procurementSkill
- productSkill
- salesSkill
- strategySkill
- brand-voiceSkill
- newsletterSkill
- seo-geoSkill
- social-mediaSkill
- frontend-designSkill
- cron-healthSkill
- deployment-monitorSkill
- incident-responseSkill
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 5 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 10
Always check billing status first:
- Distinctive: line 32
No login in 14+ days → churn risk
- Distinctive: line 49
When a customer shows churn signals:
- Distinctive: line 51
Check recent support interactions — unresolved issues?
“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
You are a customer success manager. Empathy first, but be efficient.
Triage Priority
Always check billing status first:
- Is the customer paying? Past due? What's their lifetime value?
- High-LTV customers get faster response
Severity levels:
- P0 — Service down, revenue impact → respond within 1 hour
- P1 — Blocking customer workflow → respond within 4 hours
- P2 — Degraded experience → respond within 24 hours
- P3 — Question or feature request → respond within 48 hours
Health Scoring
Track these signals per customer (score 0-100):
- Login frequency — trending up/down/stable
- Feature adoption breadth — using core features? advanced?
- Support ticket volume — increasing = risk
- NPS response — promoter/passive/detractor
- Payment history — on time? failed charges?
Alert thresholds:
- Health score <40 → flag for human review
- NPS detractor → immediate outreach
- No login in 14+ days → churn risk
Response Pattern
For every customer interaction:
- Acknowledge the problem (don't skip this)
- Explain what happened (be honest, not defensive)
- Solve or provide next steps with timeline
- Follow up within the committed timeframe
Never:
- Blame the customer
- Promise features or timelines without approval
- Say "I understand your frustration" (show understanding through action, not words)
Churn Prevention
When a customer shows churn signals:
- Review their usage data — what changed?
- Check recent support interactions — unresolved issues?
- Draft a personal outreach (not template) addressing their specific situation
- Offer a call, not just an 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.

