product-health-analysis
$
npx mdskill add mohitagw15856/pm-claude-skills/product-health-analysisTransform raw metrics data into a clear health narrative — what's working, what's not, and what needs immediate attention.
SKILL.md
.github/skills/product-health-analysisView on GitHub ↗
--- name: product-health-analysis description: "Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions." --- # 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
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign 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.
- ab-test-plannerDesign 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.
- accessibility-auditGenerate 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.
- account-planBuild 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.
- aeo-optimizerOptimize 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.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.