product-health-analysis
Product Health Analysis interprets product metrics against established goals to identify performance gaps and opportunities. Use this skill when analyzing overall product health, reviewing key performance indicators, investigating specific performance issues, generating health reports, or assessing product-market fit signals. It produces a structured report with RAG status indicators, trend analysis across acquisition, activation, engagement, and retention layers, root cause hypotheses for flagged metrics, and prioritized actions with suggested diagnostics.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/product-health-analysis && cp -r /tmp/product-health-analysis/plugins/pm-analytics/skills/product-health-analysis ~/.claude/skills/product-health-analysisSKILL.md
# Product Health Analysis Skill Transform raw metrics data into a clear health narrative — what's working, what's not, and what needs immediate attention. ## Required Inputs Ask the user for these if not provided: - **Metrics data** (current values for key metrics — even rough numbers work) - **Targets or benchmarks** (OKR targets, historical baselines, or industry benchmarks) - **Period** (week / month / quarter being analysed) - **Product area or segment** (are we looking at the whole product or a specific feature?) ## Metrics Framework Analyse across four layers: 1. **Acquisition** — new users, source quality, CAC trends 2. **Activation** — time to first value, onboarding completion rates 3. **Engagement** — DAU/MAU, feature adoption, session depth 4. **Retention** — D1/D7/D30 retention, churn rate, resurrection rate ## Process 1. For each metric, compare: current period vs. previous period, current vs. target 2. Flag anything more than 10% off target as requiring investigation 3. Look for correlations — does a drop in activation explain a retention dip 2 weeks later? 4. Write a plain-English health summary (no jargon) suitable for sharing with non-data stakeholders 5. Recommend top 3 areas for immediate investigation with suggested diagnostic steps 6. **Validate** — Confirm every flagged metric has a plausible root cause hypothesis, not just a raw number, and every recommended action has a specific owner or team ## Output Structure ### Product Health Report — [Period] **Overall Health:** 🟢 On Track / 🟡 Watch / 🔴 Action Required | Metric | Current | Target | vs. Last Period | Status | |--------|---------|--------|-----------------|--------| | [metric] | [value] | [target] | [+/-%] | [🟢/🟡/🔴] | **Key Observations:** [3-5 bullet observations written in plain English] **Areas Requiring Investigation:** 1. [Metric + hypothesis + suggested diagnostic] 2. [Metric + hypothesis + suggested diagnostic] 3. [Metric + hypothesis + suggested diagnostic] **Recommended Actions:** [Specific next steps with owners and timelines] ## Quality Checks - [ ] Every metric includes both a target and a trend (not just a snapshot) - [ ] At least one correlation is drawn between metrics (e.g., activation → retention) - [ ] Every flagged metric has a root cause hypothesis, not just "it dropped" - [ ] Observations are written for a non-technical stakeholder (no raw query language or data jargon) - [ ] Overall health rating is justified with specific evidence ## Anti-Patterns - [ ] Do not report a single aggregate metric without segment breakdowns — averages hide opposing trends - [ ] Do not flag a metric as healthy just because it is above the target — check if the target itself is meaningful - [ ] Do not list metric movements without root cause hypotheses — observations without explanations are not analysis - [ ] Do not mix product health metrics with business KPIs without explaining the relationship between them - [ ] Do not omit recommended actions — a health report that only describes problems without prioritised next steps is incomplete
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.