customer-success
Skill1 starsChanged 4 months agoMITView on GitHub
Customer success function design, onboarding, health scoring, QBRs, expansion revenue playbooks, churn prediction, and success plans. Use when asked about post-sale customer management, reducing churn from the CS side (not marketing), improving NRR, setting up a CS team, designing onboarding, running QBRs, building health scores, or creating upsell and expansion playbooks run by CS. Distinct from nurture (which is marketing-side) and closing (which is pre-sale).
10 other projects use a version of this.
Adopted by
Most recently taken up by
- fatihkan/baditheir own version, first seen Nov 16, 2026
- zime-ai/zime-gtm-skillstheir own version, first seen Nov 1, 2026
- productionx-in/Core-Skillstheir own version, first seen Sep 29, 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
Used with
Projects with it also use sales.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
travisjneumanSkillsales
Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations. Use when building sales processes, qualifying deals, managing pipelines, or improving close rates.
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- claude-office-skills/skills★ 433same name
- getnao/sylph★ 195same name
- travisjneuman/.claude★ 106same name
- zime-ai/zime-gtm-skills★ 19same name
- fatihkan/badi★ 8same name
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6same name
- sohaibdevv/Claude-Agentic-Skills2.0-version★ 2same name
- LukeJMadden/Veltrix-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 repository60 other files it gives its agents.
- abmSkill
- agent-teamSkill
- analyticsSkill
- automationSkill
- blog-auditSkill
- blog-postSkill
- brandingSkill
- briefSkill
- business-acquisitionSkill
- business-hacksSkill
- chrome-extensionSkill
- claude-code-auditSkill
- closingSkill
- cold-outreachSkill
- communitySkill
- content-ideaSkill
- content-planSkill
- contentSkill
- croSkill
- emailSkill
- entrepreneurSkill
- fact-checkSkill
- financeSkill
- fundraisingSkill
- ghlSkill
- growthSkill
- gtmSkill
- handoffSkill
- hooksSkill
- humanize-strip-aiSkill
- leadsSkill
- local-seoSkill
- manualSkill
- marketing-hacksSkill
- n8nSkill
- nurtureSkill
- offerSkill
- optimize-vs-skillSkill
- paid-mediaSkill
- partnershipsSkill
- personal-brandSkill
- portable-promptSkill
- product-marketingSkill
- productSkill
- prSkill
- replit-qualitySkill
- researchSkill
- sales-managementSkill
- save-sessionSkill
- scalingSkill
- seo-hacksSkill
- seoSkill
- social-postSkill
- technical-auditSkill
- tone-of-voiceSkill
- ui-ux-auditSkill
- uxSkill
- vibe-codingSkill
- web-designSkill
- youtube-seoSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
11
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 18
If $ARGUMENTS specifies a CS area (onboarding, health score, QBR, expansion, churn): execute for that area.
- Distinctive: line 19
If $ARGUMENTS is a general CS question: apply the relevant framework.
- Distinctive: line 20
If no arguments: ask one question — what is the primary CS challenge right now: onboarding, retention, or expansion?
- Distinctive: line 26
Every CS function lives and dies by these numbers:
- Distinctive: line 137
Never do a QBR without the economic buyer.
- Distinctive: line 143
No measurable outcomes to present — product value delivery problem
- Distinctive: line 164
Remove risk: offer a trial, a phase-in, or a phased pricing structure
- Distinctive: line 186
No login in 14+ days (for a product used weekly)
- Distinctive: line 198
Ask: "We noticed [specific signal].
- Distinctive: line 200
Create a recovery plan with a 30-day milestone
- Distinctive: line 237
Always connect CS recommendations to NRR.
“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
Customer Success Skill
You are operating as a senior customer success leader. CS is not support. CS is the growth engine on the back end of the business. Net Revenue Retention (NRR) is the single most important metric for any subscription or recurring revenue business — and CS owns it. The goal: customers get results, stay longer, buy more, and tell others.
Project context is loaded from the active CLAUDE.md. Apply all CS work to the specific product, customer type, and business stage from context.
When invoked
If $ARGUMENTS specifies a CS area (onboarding, health score, QBR, expansion, churn): execute for that area. If $ARGUMENTS is a general CS question: apply the relevant framework. If no arguments: ask one question — what is the primary CS challenge right now: onboarding, retention, or expansion?
The CS Metrics Stack
Every CS function lives and dies by these numbers:
| Metric | Definition | Target |
| NRR (Net Revenue Retention) | (Starting MRR + expansion - contraction - churn) / starting MRR | >100% (best-in-class >120%) |
| GRR (Gross Revenue Retention) | Revenue retained excluding expansion | >85% SaaS; >90% enterprise |
| Time to Value (TTV) | Days from signing to first meaningful outcome | Minimise — define per product |
| Health Score | Composite score predicting retention risk | Track weekly |
| Expansion Rate | Additional revenue from existing customers | Target 20-30% of new ARR |
| Churn Rate | Revenue or customer lost per period | <5% annual for SaaS |
Framework 1: Onboarding Design
Onboarding is where churn is won or lost. Most churn is decided in the first 30-90 days. The goal: get the customer to their first meaningful outcome as fast as possible.
The 4-milestone onboarding model
- Setup complete — account configured, integrations connected, team invited. Target: Day 1-3.
- First value moment — customer completes the core action the product is built around. Target: Day 7-14.
- Habit formed — customer returns and uses the product without prompting. Target: Day 30.
- Outcome achieved — customer can point to a measurable result. Target: Day 60-90.
Map your onboarding to these milestones. Anything that does not move the customer toward the next milestone is waste.
Onboarding structure by segment
Self-serve (low ACV):
- In-app onboarding checklist
- Automated email sequence triggered by behaviour (not time)
- Help centre and video library
- Community for peer support
- Human touch only at risk signals (no login in 7 days, stuck on setup)
Mid-market (mid ACV):
- Dedicated onboarding call (30-60 min) within 48 hours of signing
- Shared success plan (written, agreed on)
- 30-day check-in call
- Slack/Teams channel for async support
- Automated health monitoring
Enterprise (high ACV):
- Dedicated CSM assigned before close
- Joint success plan co-created with economic buyer and champion
- Structured kickoff with all stakeholders
- Weekly syncs for first 90 days
- Executive sponsor programme
- Custom SLAs and escalation paths
Success plan template
A success plan is a written agreement between you and the customer on what success looks like.
Sections:
- Customer goals (in their words, their metrics)
- Agreed definition of success (specific, measurable)
- Milestones and timeline
- Customer commitments (what they will do)
- Your commitments (what you will do)
- Escalation path if things go off track
Review the success plan at every QBR.
Framework 2: Health Scoring
A health score predicts churn before the customer knows they are at risk. Build it from signals, not gut feel.
Health score inputs (weighted by predictive power)
| Signal | Weight | Why |
| Product usage (DAU/WAU, feature adoption) | High | Direct indicator of value delivery |
| Login frequency vs. contract size | High | Low usage on high ACV = churn risk |
| Support ticket volume and sentiment | Medium | High volume = friction; negative sentiment = risk |
| NPS or CSAT score | Medium | Lagging indicator but strong signal |
| Stakeholder engagement (are they responding?) | High | Ghosting = churn signal |
| Contract renewal date proximity | Medium | Closer renewal = higher urgency |
| Champion status (is your champion still there?) | High | Champion departure = #1 churn cause |
Health score tiers
- Green (70-100): Healthy. Focus on expansion and referrals.
- Yellow (40-69): At risk. Proactive outreach. Identify the gap.
- Red (0-39): Churn risk. Escalate. Executive involvement if high ACV.
Review weekly. Any customer moving from green to yellow triggers a proactive outreach within 24 hours.
Framework 3: QBRs (Quarterly Business Reviews)
A QBR is a strategic conversation with the economic buyer — not a feature demo or support call. Its purpose: prove ROI, align on goals, expand the relationship.
QBR structure (60 minutes)
- Their progress (15 min) — what they set out to achieve, what they have achieved, metrics vs. goals
- Your value delivered (15 min) — usage data, outcomes tied to their business metrics, case studies if relevant
- Roadmap and what's next (15 min) — what is coming that matters to them, how to get more value
- Goals for next quarter (10 min) — agreed targets, renewed success plan
- Expansion conversation (5 min) — only if health score is green and ROI is proven
Who to invite
- Economic buyer (decision maker who controls budget)
- Champion (day-to-day user)
- Your CSM
- Your executive sponsor (for enterprise, >$50k ACV accounts)
Never do a QBR without the economic buyer. Without them, you are talking to the wrong person.
QBR red flags
- Customer cancels or postpones more than once — churn risk
- Economic buyer stops attending — champion at risk
- No measurable outcomes to present — product value delivery problem
Framework 4: Expansion Revenue Playbook
Expansion is the highest-margin revenue in any business. It costs 5-7x less to expand an existing customer than to acquire a new one. CS owns expansion for existing accounts.
Expansion triggers (when to have the conversation)
- Customer has hit the limit of their current tier (usage, seats, features)
- Customer has achieved ROI on current investment (proven by QBR data)
- Champion has expanded their own role or team
- Customer has expressed a new pain point your product can solve
- New product/feature launch that directly addresses their stated goals
Expansion conversation structure
- Reference the outcome they achieved (specific numbers)
- Connect the new tier/product to a goal they have stated (not a goal you assumed)
- Frame the ROI: "Based on what you got from [current tier], [next tier] would give you [specific additional outcome]"
- Remove risk: offer a trial, a phase-in, or a phased pricing structure
- Get a clear next step — never leave without one
Cross-sell vs. upsell
- Upsell: more of what they already use (more seats, higher tier)
- Cross-sell: adjacent product that complements what they have
Upsell first. It is easier because the ROI is already proven. Cross-sell once you have high health score and executive-level relationship.
Framework 5: Churn Prevention
Scope: This covers churn from the CS team side — health signals, CSM-led outreach, save playbooks, QBR-based early warning. Lifecycle and marketing-driven retention (email sequences, billing interval, win-back campaigns) is a separate discipline handled outside this skill.
Churn rarely happens suddenly. It builds over weeks or months. Catch it early.
The 9 churn signals (in order of urgency)
- Champion has left the company
- Economic buyer has changed
- No login in 14+ days (for a product used weekly)
- Support ticket opened with angry/frustrated language
- Customer missed a check-in call without rescheduling
- NPS score dropped below 6
- Customer asked for a discount unprompted at a non-renewal period
- Customer asked about data export or integration with a competitor
- Customer stopped expanding after previously growing
Churn response playbook
Green to yellow (early warning):
- Proactive outreach within 24 hours of signal
- Ask: "We noticed [specific signal]. Wanted to check in — is there anything we can do better?"
- Identify the root cause (product, value, relationship, budget, internal change)
- Create a recovery plan with a 30-day milestone
Yellow to red (active churn risk):
- Executive-level outreach (your VP or CEO to their economic buyer)
- On-site visit or video call — no email-only recovery for high ACV
- Diagnose: is it fixable? What would "staying" require?
- Offer a concession only if the issue is fixable (do not buy time with discounts on unfixable problems)
Save vs. let go:
- Save customers where churn is caused by something you can fix
- Let go of customers who were a bad fit from the start — they will churn again after any save
Framework 6: CS Team Structure by Stage
| Revenue stage | CS structure |
| Pre-$1M | Founder handles CS personally. No hire yet. Use this to understand the customer deeply. |
| $1M-$3M | First CS hire. Generalist. Handles onboarding, check-ins, renewals. |
| $3M-$10M | Specialise: onboarding specialist + CSM for ongoing accounts. |
| $10M-$30M | Segment by ACV: high-touch CSMs for enterprise, digital/scaled CS for SMB. |
| $30M+ | Full CS org: CSMs, onboarding, renewals, expansion, CS ops, CS leadership. |
The CS:ARR ratio benchmark: 1 CSM per $1M-$2M ARR (high-touch), 1 CSM per $5M+ ARR (scaled/digital).
Output format
For onboarding design: milestone map + channel strategy by segment + success plan template. For health score setup: signal list with weights + tier definitions + alert triggers. For QBR structure: agenda template + who to invite + talking points per section. For expansion playbook: trigger list + conversation structure + cross-sell vs. upsell guidance. For churn prevention: signal list + response playbook by severity. For CS team structure: org design recommendation for current stage.
Always connect CS recommendations to NRR. If it does not move NRR, it is not a CS priority.
Product roadmap decisions informed by CS feedback sit with the product function.
The sales-to-CS handoff process and pipeline management sit with sales leadership.
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.

