skills/retention-analysis/SKILL.md
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.
npx skillsauth add mohitagw15856/pm-claude-skills retention-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.
Diagnose why users leave, identify what keeps them, and recommend specific, testable interventions — not vague "improve onboarding" suggestions.
The retention curve has two components:
A product with PMF has a retention curve that flattens. If it trends to zero, you have a PMF problem, not an onboarding problem. Name this distinction explicitly.
| Metric | Formula | What It Tells You | |---|---|---| | D1 Retention | Users who return on day 2 ÷ new users day 1 | Quality of first experience | | D7 Retention | Users active on day 8 ÷ users who joined 7 days ago | Early habit formation | | D30 Retention | Users active on day 31 ÷ users who joined 30 days ago | Product-market fit signal | | DAU/MAU Ratio | Daily active users ÷ monthly active users | Stickiness (>20% good, >50% excellent) | | Churn Rate | Users lost in period ÷ users at start of period | Monthly or annual | | Net Revenue Retention | MRR at end of period ÷ MRR at start (same cohort) | Revenue health including expansion |
Don't analyse "retention" — analyse retention for specific cohorts:
Where does the drop happen? D1? D7? Month 3?
Which early behaviour predicts long-term retention?
Interview churned users — never skip this. Survey data alone is insufficient.
Question: [Specific retention question being answered] Period Analysed: [Date range] Segment: [Which users]
Current Retention Snapshot:
| Metric | Current | Industry Benchmark | Status | |---|---|---|---| | D1 Retention | [X%] | 25–40% | 🔴/🟡/🟢 | | D7 Retention | [X%] | 10–25% | 🔴/🟡/🟢 | | D30 Retention | [X%] | 5–15% | 🔴/🟡/🟢 | | DAU/MAU | [X%] | 10–20% typical | 🔴/🟡/🟢 |
Retention Curve Shape: [Flattening / Still declining / Trending to zero] PMF Signal: [Strong / Weak / Absent — based on curve shape]
Root Cause Hypotheses:
| Hypothesis | Evidence | Confidence | Test | |---|---|---|---| | [Cause] | [Data point] | H/M/L | [How to validate] |
"Aha Moment" Correlation: Users who [specific action] in first [N] days retain at [X%] vs [Y%] for those who don't.
Recommended Interventions:
| Intervention | Target Drop | Expected Lift | Effort | Priority | |---|---|---|---|---| | [Specific change] | D1 / D7 / D30 | [X%] | S/M/L | 1/2/3 |
Monitoring Plan:
Ask the user for these if not provided:
development
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
development
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
development
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
development
Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.