plugins/pm-cs/skills/churn-analysis/SKILL.md
Analyse customer churn for a product or cohort and produce a structured churn report. Use when asked to analyse churn, understand why customers are leaving, identify churn patterns, calculate churn rate, or build a churn reduction plan. Produces a churn analysis with rate calculations, categorised reasons, early warning signals, and prioritised interventions.
npx skillsauth add mohitagw15856/pm-claude-skills churn-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produce a structured churn analysis that goes beyond the headline rate — identifying why customers leave, which segments are most at risk, and what interventions will have the highest impact on retention.
Ask for these if not already provided:
Always classify churn before analysing it:
| Category | Definition | |---|---| | Voluntary — avoidable | Customer left due to a problem we could have addressed (product gaps, poor onboarding, relationship failures) | | Voluntary — unavoidable | Customer left for reasons outside our control (budget cuts, acquisition, company shutdown) | | Involuntary | Payment failure, contract non-renewal by mistake, admin error |
The interventions for each category are different. Conflating them leads to wrong conclusions.
Period: [Start date] — [End date] Prepared by: [Name] | Date: [Date]
| Metric | Value | |---|---| | Customers at start of period | [N] | | Customers churned | [N] | | Customer churn rate | [X]% | | ARR at start of period | £/$/€[X] | | ARR lost to churn | £/$/€[X] | | Revenue churn rate (gross) | [X]% | | ARR from expansions (same period) | £/$/€[X] | | Net revenue retention (NRR) | [X]% |
Benchmark context:
| Category | Customers | % of churn | ARR lost | |---|---|---|---| | Voluntary — avoidable | [N] | [X]% | £/$/€[X] | | Voluntary — unavoidable | [N] | [X]% | £/$/€[X] | | Involuntary | [N] | [X]% | £/$/€[X] | | Total | [N] | 100% | £/$/€[X] |
Avoidable churn as % of total churn: [X]% — this is the number we can actually influence.
Rank by frequency. Include ARR weight where data allows.
| Reason | Count | % of avoidable churn | ARR lost | Representative quote | |---|---|---|---|---| | [Reason 1 — e.g. "Product missing key feature"] | [N] | [X]% | £/$/€[X] | "[Quote]" | | [Reason 2] | [N] | [X]% | £/$/€[X] | "[Quote]" | | [Reason 3] | [N] | [X]% | £/$/€[X] | "[Quote]" | | [Reason 4] | [N] | [X]% | £/$/€[X] | "[Quote]" | | Other | [N] | [X]% | £/$/€[X] | — |
Theme synthesis: [2–3 sentences grouping the top reasons into 2–3 themes. E.g. "The top three reasons cluster around two themes: product gaps in [area] (affecting X% of avoidable churn) and onboarding failures where customers never achieved value (Y%)."]
Identify which segments over- or under-index for churn.
| Tier | Churn rate | vs. Overall | Notes | |---|---|---|---| | Enterprise | [X]% | +/-[X]pp | | | Mid-Market | [X]% | +/-[X]pp | | | SMB | [X]% | +/-[X]pp | |
| Cohort | Churn rate | Notes | |---|---|---| | [Year 1] | [X]% | | | [Year 2] | [X]% | | | [Year 3] | [X]% | |
| Segment | Churn rate | Notes | |---|---|---| | [Segment 1] | [X]% | | | [Segment 2] | [X]% | |
Key pattern: [Which segment has the highest churn rate and what likely explains it]
| When churn occurred | % of churned accounts | |---|---| | 0–3 months | [X]% | | 3–6 months | [X]% | | 6–12 months | [X]% | | 12+ months | [X]% |
Based on the churned accounts, identify the signals that preceded churn (and could have triggered earlier intervention):
| Signal | Lead time before churn | How to detect | |---|---|---| | [Signal 1 — e.g. "DAU/MAU dropped below 15%"] | [~X weeks] | [Usage dashboard / alert] | | [Signal 2 — e.g. "No QBR in 90+ days"] | [~X weeks] | [CRM flag] | | [Signal 3 — e.g. "Champion left the account"] | [~X weeks] | [LinkedIn alert / CSM tracking] | | [Signal 4] | [~X weeks] | [Detection method] |
Ranked by estimated impact × feasibility.
| Intervention | Addresses | Est. churn reduction | Effort | Owner | |---|---|---|---|---| | [Intervention 1 — e.g. "Improve onboarding for [segment] with dedicated 30-day check-in"] | [Reason 1] | [X accounts / £X ARR] | Low / Med / High | [Team] | | [Intervention 2] | [Reason 2] | [X accounts / £X ARR] | Low / Med / High | [Team] | | [Intervention 3] | [Reason 3] | [X accounts / £X ARR] | Low / Med / High | [Team] |
Priority call: [Which one intervention, if implemented this quarter, would have the biggest impact and why]
development
Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with hook formulas, content structures, shareability triggers, and a content testing system.
development
Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and returns ranked candidates with rationale. Use when asked to create thumbnails, generate cover images, or produce visual candidates for an article or newsletter.
testing
Flips Claude's default from "find reasons you're right" to "find reasons you're wrong." A genuine thinking partner, not a mirror with grammar. Use before high-stakes decisions, plans, assumptions, or pitches you haven't stress-tested.
development
Scrapes a Substack Notes page and exports engagement data (likes, comments, restacks) to a formatted .xlsx file with conditional formatting and summary stats.