product-analytics
$
npx mdskill add alirezarezvani/claude-skills/product-analyticsAnalyzes and defines product metrics for growth and optimization
- Tracks KPIs and trends for product stages from discovery to maturity
- Leverages analytics tools and user data sources for insights
- Applies frameworks like AARRR, North Star, and HEART for metric alignment
- Delivers actionable dashboards and cohort analysis for decision-making
SKILL.md
.github/skills/product-analyticsView on GitHub ↗
--- name: product-analytics description: Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages. --- # Product Analytics Define, track, and interpret product metrics across discovery, growth, and mature product stages. ## When To Use Use this skill for: - Metric framework selection (AARRR, North Star, HEART) - KPI definition by product stage (pre-PMF, growth, mature) - Dashboard design and metric hierarchy - Cohort and retention analysis - Feature adoption and funnel interpretation ## Workflow 1. Select metric framework - AARRR for growth loops and funnel visibility - North Star for cross-functional strategic alignment - HEART for UX quality and user experience measurement 2. Define stage-appropriate KPIs - Pre-PMF: activation, early retention, qualitative success - Growth: acquisition efficiency, expansion, conversion velocity - Mature: retention depth, revenue quality, operational efficiency 3. Design dashboard layers - Executive layer: 5-7 directional metrics - Product health layer: acquisition, activation, retention, engagement - Feature layer: adoption, depth, repeat usage, outcome correlation 4. Run cohort + retention analysis - Segment by signup cohort or feature exposure cohort - Compare retention curves, not single-point snapshots - Identify inflection points around onboarding and first value moment 5. Interpret and act - Connect metric movement to product changes and release timeline - Distinguish signal from noise using period-over-period context - Propose one clear product action per major metric risk/opportunity ## KPI Guidance By Stage ### Pre-PMF - Activation rate - Week-1 retention - Time-to-first-value - Problem-solution fit interview score ### Growth - Funnel conversion by stage - Monthly retained users - Feature adoption among new cohorts - Expansion / upsell proxy metrics ### Mature - Net revenue retention aligned product metrics - Power-user share and depth of use - Churn risk indicators by segment - Reliability and support-deflection product metrics ## Dashboard Design Principles - Show trends, not isolated point estimates. - Keep one owner per KPI. - Pair each KPI with target, threshold, and decision rule. - Use cohort and segment filters by default. - Prefer comparable time windows (weekly vs weekly, monthly vs monthly). See: - `references/metrics-frameworks.md` - `references/dashboard-templates.md` ## Cohort Analysis Method 1. Define cohort anchor event (signup, activation, first purchase). 2. Define retained behavior (active day, key action, repeat session). 3. Build retention matrix by cohort week/month and age period. 4. Compare curve shape across cohorts. 5. Flag early drop points and investigate journey friction. ## Retention Curve Interpretation - Sharp early drop, low plateau: onboarding mismatch or weak initial value. - Moderate drop, stable plateau: healthy core audience with predictable churn. - Flattening at low level: product used occasionally, revisit value metric. - Improving newer cohorts: onboarding or positioning improvements are working. ## Anti-Patterns | Anti-pattern | Fix | |---|---| | **Vanity metrics** — tracking pageviews or total signups without activation context | Always pair acquisition metrics with activation rate and retention | | **Single-point retention** — reporting "30-day retention is 20%" | Compare retention curves across cohorts, not isolated snapshots | | **Dashboard overload** — 30+ metrics on one screen | Executive layer: 5-7 metrics. Feature layer: per-feature only | | **No decision rule** — tracking a KPI with no threshold or action plan | Every KPI needs: target, threshold, owner, and "if below X, then Y" | | **Averaging across segments** — reporting blended metrics that hide segment differences | Always segment by cohort, plan tier, channel, or geography | | **Ignoring seasonality** — comparing this week to last week without adjusting | Use period-over-period with same-period-last-year context | ## Tooling ### `scripts/metrics_calculator.py` CLI utility for retention, cohort, and funnel analysis from CSV data. Supports text and JSON output. ```bash # Retention analysis python3 scripts/metrics_calculator.py retention events.csv python3 scripts/metrics_calculator.py retention events.csv --format json # Cohort matrix python3 scripts/metrics_calculator.py cohort events.csv --cohort-grain month python3 scripts/metrics_calculator.py cohort events.csv --cohort-grain week --format json # Funnel conversion python3 scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay python3 scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay --format json ``` **CSV format for retention/cohort:** ```csv user_id,cohort_date,activity_date u001,2026-01-01,2026-01-01 u001,2026-01-01,2026-01-03 u002,2026-01-02,2026-01-02 ``` **CSV format for funnel:** ```csv user_id,stage u001,visit u001,signup u001,activate u002,visit u002,signup ``` ## Cross-References - Related: `product-team/experiment-designer` — for A/B test planning after identifying metric opportunities - Related: `product-team/product-manager-toolkit` — for RICE prioritization of metric-driven features - Related: `product-team/product-discovery` — for assumption mapping when metrics reveal unknowns - Related: `finance/saas-metrics-coach` — for SaaS-specific metrics (ARR, MRR, churn, LTV)
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.