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:
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.