Product analytics

Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/product-analytics.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/product-team/skills/product-analytics#main ~/.claude/skills/product-analytics

For one project only, change the path to .claude/skills/product-analytics.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Product analytics

Show the full text148 lines
namedescription
product-analyticsUse 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
  1. Define stage-appropriate KPIs
  • Pre-PMF: activation, early retention, qualitative success
  • Growth: acquisition efficiency, expansion, conversion velocity
  • Mature: retention depth, revenue quality, operational efficiency
  1. Design dashboard layers
  • Executive layer: 5-7 directional metrics
  • Product health layer: acquisition, activation, retention, engagement
  • Feature layer: adoption, depth, repeat usage, outcome correlation
  1. 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
  1. 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.

# 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:

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:

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)
1---
2name: product-analytics
3description: Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.
4---
5 
6# Product Analytics
7 
8Define, track, and interpret product metrics across discovery, growth, and mature product stages.
9 
10## When To Use
11 
12Use this skill for:
13- Metric framework selection (AARRR, North Star, HEART)
14- KPI definition by product stage (pre-PMF, growth, mature)
15- Dashboard design and metric hierarchy
16- Cohort and retention analysis
17- Feature adoption and funnel interpretation
18 
19## Workflow
20 
211. Select metric framework
22- AARRR for growth loops and funnel visibility
23- North Star for cross-functional strategic alignment
24- HEART for UX quality and user experience measurement
25 
262. Define stage-appropriate KPIs
27- Pre-PMF: activation, early retention, qualitative success
28- Growth: acquisition efficiency, expansion, conversion velocity
29- Mature: retention depth, revenue quality, operational efficiency
30 
313. Design dashboard layers
32- Executive layer: 5-7 directional metrics
33- Product health layer: acquisition, activation, retention, engagement
34- Feature layer: adoption, depth, repeat usage, outcome correlation
35 
364. Run cohort + retention analysis
37- Segment by signup cohort or feature exposure cohort
38- Compare retention curves, not single-point snapshots
39- Identify inflection points around onboarding and first value moment
40 
415. Interpret and act
42- Connect metric movement to product changes and release timeline
43- Distinguish signal from noise using period-over-period context
44- Propose one clear product action per major metric risk/opportunity
45 
46## KPI Guidance By Stage
47 
48### Pre-PMF
49- Activation rate
50- Week-1 retention
51- Time-to-first-value
52- Problem-solution fit interview score
53 
54### Growth
55- Funnel conversion by stage
56- Monthly retained users
57- Feature adoption among new cohorts
58- Expansion / upsell proxy metrics
59 
60### Mature
61- Net revenue retention aligned product metrics
62- Power-user share and depth of use
63- Churn risk indicators by segment
64- Reliability and support-deflection product metrics
65 
66## Dashboard Design Principles
67 
68- Show trends, not isolated point estimates.
69- Keep one owner per KPI.
70- Pair each KPI with target, threshold, and decision rule.
71- Use cohort and segment filters by default.
72- Prefer comparable time windows (weekly vs weekly, monthly vs monthly).
73 
74See:
75- `references/metrics-frameworks.md`
76- `references/dashboard-templates.md`
77 
78## Cohort Analysis Method
79 
801. Define cohort anchor event (signup, activation, first purchase).
812. Define retained behavior (active day, key action, repeat session).
823. Build retention matrix by cohort week/month and age period.
834. Compare curve shape across cohorts.
845. Flag early drop points and investigate journey friction.
85 
86## Retention Curve Interpretation
87 
88- Sharp early drop, low plateau: onboarding mismatch or weak initial value.
89- Moderate drop, stable plateau: healthy core audience with predictable churn.
90- Flattening at low level: product used occasionally, revisit value metric.
91- Improving newer cohorts: onboarding or positioning improvements are working.
92 
93## Anti-Patterns
94 
95| Anti-pattern | Fix |
96|---|---|
97| **Vanity metrics** — tracking pageviews or total signups without activation context | Always pair acquisition metrics with activation rate and retention |
98| **Single-point retention** — reporting "30-day retention is 20%" | Compare retention curves across cohorts, not isolated snapshots |
99| **Dashboard overload** — 30+ metrics on one screen | Executive layer: 5-7 metrics. Feature layer: per-feature only |
100| **No decision rule** — tracking a KPI with no threshold or action plan | Every KPI needs: target, threshold, owner, and "if below X, then Y" |
101| **Averaging across segments** — reporting blended metrics that hide segment differences | Always segment by cohort, plan tier, channel, or geography |
102| **Ignoring seasonality** — comparing this week to last week without adjusting | Use period-over-period with same-period-last-year context |
103 
104## Tooling
105 
106### `scripts/metrics_calculator.py`
107 
108CLI utility for retention, cohort, and funnel analysis from CSV data. Supports text and JSON output.
109 
110```bash
111# Retention analysis
112python3 scripts/metrics_calculator.py retention events.csv
113python3 scripts/metrics_calculator.py retention events.csv --format json
114 
115# Cohort matrix
116python3 scripts/metrics_calculator.py cohort events.csv --cohort-grain month
117python3 scripts/metrics_calculator.py cohort events.csv --cohort-grain week --format json
118 
119# Funnel conversion
120python3 scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay
121python3 scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay --format json
122```
123 
124**CSV format for retention/cohort:**
125```csv
126user_id,cohort_date,activity_date
127u001,2026-01-01,2026-01-01
128u001,2026-01-01,2026-01-03
129u002,2026-01-02,2026-01-02
130```
131 
132**CSV format for funnel:**
133```csv
134user_id,stage
135u001,visit
136u001,signup
137u001,activate
138u002,visit
139u002,signup
140```
141 
142## Cross-References
143 
144- Related: `product-team/experiment-designer` — for A/B test planning after identifying metric opportunities
145- Related: `product-team/product-manager-toolkit` — for RICE prioritization of metric-driven features
146- Related: `product-team/product-discovery` — for assumption mapping when metrics reveal unknowns
147- Related: `finance/saas-metrics-coach` — for SaaS-specific metrics (ARR, MRR, churn, LTV)
148 

Discussion

Alternatives

Also in Reports & dashboardsSee all 47 in Data & analytics →
/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.Data & AI · MITPath A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Creator · MIT