The 3 Claude Skills That Keep Customers From Leaving
Customer success is reactive at most companies. You hear something is wrong when the client tells you, and by then you're already in damage control. The accounts that churn are usually the ones where the signals were there — engagement dropped, the QBR was rescheduled twice, the champion left — and nobody put them together in time.
The Customer Success pack has 4 skills. Here are the three that shift you from reactive to ahead of it.
/churn-risk
When a client is thinking about leaving, they usually don't say so directly. What they do is get quieter. They stop responding as fast. They cancel a check-in. They ask a question that reveals they're not using a feature they said was important to them. These signals are there if you know what to look for.
/churn-risk takes a description of a client relationship — recent interactions, usage patterns, open issues, any red flags you've noticed — and diagnoses whether the account is at risk and why. Then it gives you a concrete 3-step save plan, not a list of things to monitor.
--email drafts the re-engagement email as part of the output so you can act on the diagnosis immediately. --renewal-prep structures the output as prep for an upcoming renewal conversation, framing the risk and the response as part of the renewal strategy.
Catching churn early is almost always easier than reversing it once the decision is made.
/onboarding-plan
The first 30 days of a client relationship set the pattern for everything that follows. Clients who get a structured onboarding with clear milestones, defined owners, and consistent communication become long-term accounts. Clients who get a login and a "let us know if you have questions" email churn quietly three months later and say the product wasn't what they expected.
/onboarding-plan builds a structured 30-day onboarding plan for any new client — tasks, owners, milestones, and a welcome email. Everything a new client needs to feel like someone thought through what success looks like for them specifically.
--email writes the full welcome email sequence alongside the plan. --async formats the plan for async-first teams where synchronous check-ins aren't the primary communication mode.
What happens in the first 30 days is the strongest predictor of whether a client stays or leaves. This makes sure something actually happens.
/case-study
Happy customers are your best marketing and most teams underuse them. The story exists — the client had a problem, they used your product, something improved — but writing it up takes time nobody prioritizes, and by the time someone does it, the details have faded.
/case-study writes a compelling customer case study from a quick brief. Specific results, real numbers where you have them, no generic "we were impressed by their innovative approach" filler. The kind of case study that reads like proof rather than a testimonial.
--short produces a condensed version for use on a landing page or in a sales deck. --interview generates the interview questions to use with the customer so you can collect the details you need before writing.
A case study you actually publish is worth more than a perfect one you're still drafting.
All four skills in the Customer Success pack — including /qbr-prep for quarterly business review agendas and talking points — are available to Skills Pack members. They ship as SKILL.md files — drop them into ~/.claude/skills/ and invoke with the slash command in Claude Code, Cursor, or Codex.
Next up: the Executive Assistant pack — email triage, meeting prep, follow-ups, investor updates, and weekly briefs.