pm-metrics
Systematically analyzes product metrics to uncover trends, identify anomalies, and provide actionable business recommendations.
Install
mkdir -p .claude/skills/pm-metrics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19507" && unzip -o skill.zip -d .claude/skills/pm-metrics && rm skill.zipInstalls to .claude/skills/pm-metrics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked only — do NOT auto-trigger. Triggers on /pm-metrics, "обзор метрик", "разбор воронки", "анализ удержания", "ретеншн", "A/B результаты", "review metrics", "DAU analysis", "retention analysis", "funnel analysis", "metric anomaly".Key capabilities
- →Decompose North Star metrics into L1/L2 dimensions
- →Diagnose retention curves and funnel bottlenecks
- →Interpret A/B experiment results
- →Identify root causes for metric anomalies
How it works
It uses a framework to decompose North Star metrics, analyze growth and retention segments, and identify bottlenecks in conversion funnels to provide actionable insights.
Inputs & outputs
When to use pm-metrics
- →Review weekly product performance metrics
- →Analyze retention curve drops
- →Interpret results from A/B experiments
- →Decompose North Star metrics into L1/L2
About this skill
pm-metrics — Product metrics review
Part of the Personal Corp framework — running a one-person business through AI agents. Systematically review product metrics, identify trend changes, locate root causes, output action recommendations. Includes North Star decomposition, retention diagnostics, funnel methodology, and A/B experiment reading.
Inputs
| Field | Required | Notes |
|---|---|---|
| Metric data | yes | Excel / CSV / pasted table / verbal description |
| Cycle | no | Weekly / monthly / quarterly review; default weekly |
| Focus | no | Full review / single-metric anomaly / experiment readout |
| Business context | no | Releases, campaigns, incidents in the period |
Mode: full data → complete review; single-metric change → focused anomaly analysis.
Step 1 — Data integrity check
- Confirm time coverage (current vs comparison period)
- Confirm metric coverage (which North Star / L1 / L2 are present)
- Flag missing critical data
Step 2 — North Star metric system
Decomposition: North Star → L1 → L2.
L1 dimensions:
- User growth: DAU/WAU/MAU, new, returning
- User engagement: core action frequency, session length, feature reach
- User retention: D1 / D7 / D30
- Conversion efficiency: signup → activation → paid step-by-step rates
- Business value: paid rate, ARPU, LTV
- Satisfaction: NPS, complaint rate, ratings
North Star selection guide:
| Product type | Recommended NSM | Typical L1 |
|---|---|---|
| Social / community | Weekly active posters | DAU/MAU ratio, interactions per user, D7 retention |
| Tools / productivity | Weekly users completing core task | Task completion rate, frequency, feature reach |
| E-commerce | Weekly transacting users | GMV, AOV, repeat rate, conversion |
| Content / media | Weekly content-consumption time | Time per user, completion rate, return rate |
| SaaS / B2B | Weekly active teams | Team penetration, feature depth, renewal rate |
Step 3 — Growth metric analysis
Definitions:
- DAU: distinct users with valid action that day
- WAU: distinct users active ≥ 1 day in 7
- MAU: distinct users active ≥ 1 day in 30
- DAU/MAU ratio (stickiness): > 0.5 very high, 0.3-0.5 high, 0.2-0.3 medium, < 0.2 low
User segmentation:
| Type | Definition | Focus |
|---|---|---|
| New | First-time user | Channel quality, activation rate |
| Active retained | Active in both periods | Depth, feature reach |
| Returning | Inactive last period, active this | Return reason, secondary retention |
| Churned | Active last period, inactive this | Churn cause, win-back potential |
| Dormant | Inactive multiple periods | Possibly permanent loss |
Growth identity: This-period MAU = prev-period retained + new + returning − churned
Step 4 — Retention analysis
Definitions:
- D1: % of new users who return on day 2
- D7: % of new users who return on day 8
- D30: % of new users who return on day 31
Retention benchmarks:
| Product type | D1 | D7 | D30 | Note |
|---|---|---|---|---|
| Social / messaging | > 70% | > 50% | > 35% | High-frequency essential |
| Tools | > 40% | > 25% | > 15% | "Use and leave" pattern |
| Content / news | > 35% | > 20% | > 10% | Many alternatives, lower retention |
| E-commerce | > 25% | > 15% | > 8% | Low-frequency, watch repeat rate instead |
| Games | > 40% | > 20% | > 10% | High variance by genre |
| SaaS / B2B | > 60% | > 45% | > 30% | High switching cost, higher baseline |
Retention-curve diagnosis:
- Steep drop (D1 → D7 loses > 60%): activation experience broken — users didn't find value
- Slow decay (D7 → D30 keeps falling, doesn't level): no long-term hook
- L-shape (levels off after D7): healthy, core user base formed
- Bounce-back (sudden uptick on a specific day): cyclical use pattern (e.g. weekday-only)
Retention segmentation:
- By channel: organic vs paid retention gap
- By behavior: completed activation vs not
- By cohort month: compare month-over-month curves to gauge product improvement
Step 5 — Conversion funnel analysis
Funnel construction:
- Define start and end points (e.g. homepage visit → payment success)
- Split into key intermediate steps (each step = a user decision point)
- Per-step rate = arriving at next / arriving at this
Funnel framework:
| Step | Action | Output |
|---|---|---|
| Draw | List steps + rates | Full funnel view |
| Identify bottleneck | Find lowest-rate step | Optimization focus |
| Benchmark | Compare history / industry / competitor | Gap quantification |
| Segment | By channel / device / user type | Locate problem cohort |
| Hypothesize | Why is the bottleneck there? | Optimization direction |
| Experiment | Propose A/B test | Action plan |
Common funnels:
- Acquisition: impression → click → install/signup → activation
- Activation: signup → onboarding done → core action first-trigger
- Payment: browse → cart → order → pay success
- Sharing: trigger → share click → recipient open → recipient conversion
Step 6 — A/B experiment readout
| Dimension | Standard | Note |
|---|---|---|
| Statistical significance | p < 0.05 | p > 0.05 → inconclusive, don't decide |
| Effect size | Lift > MDE | Significant but tiny lift may not be worth it |
| Sample size | Reaches pre-set N | "Significant" without N is unreliable |
| Duration | Covers ≥ 1-2 full weeks | Avoid weekday/weekend bias |
| AA check | Pre-period baselines match | Mismatch → split assignment is broken |
Decision framework:
- Significant + large effect → ship to all
- Significant + small effect → weigh long-term value vs cost
- Not significant → don't ship; investigate (wrong hypothesis? sample? execution?)
- Metric conflict (A up, B down) → weigh, prioritize North Star
Common pitfalls:
- Reading results too early (before reaching N)
- Looking only at primary metric, not guardrails
- Multiple peeks → false positives
- Ignoring novelty effect (early data inflated)
Step 7 — OKR alignment check
| Check | Healthy | Anomaly signal |
|---|---|---|
| Coverage | Every KR has ≥ 1 trackable metric | A KR with no measurable proxy |
| Consistency | Metric direction matches KR target | Metric up but KR no progress |
| Pacing | Linear pacing ≥ 50% by mid-quarter | Severely behind schedule |
| Attribution | Metric movement attributable to team action | Metric improved due to industry tailwind, not team |
OKR progress table:
| OKR | KR metric | Target | Current | Progress % | Trend | Risk |
|---|---|---|---|---|---|---|
| {O1} | {KR1} | {target} | {current} | {X%} | Up/flat/down | On-track / at-risk / severe |
Step 8 — Anomaly attribution
When a metric moves anomalously, work the framework:
- Quantify: how much, starting when?
- Decompose: segment by channel / region / version / cohort to localize
- Time-align: what happened around the inflection? (release, campaign, incident, competitor move)
- Eliminate: rule out causes one by one until the most likely root remains
- Cross-check: verify the attribution via other metrics
Common causes:
| Category | Pattern | Verification |
|---|---|---|
| Release | Inflection aligns with deploy time | Compare per-version |
| Campaign | Up during campaign, drops after | Compare per-channel |
| Tech incident | Sudden drop + recovery | Check error logs and uptime |
| External | Industry-wide change | Compare with competitor / industry data |
| Channel mix | One channel changed dramatically | Per-channel decomposition |
| Seasonality | Same as YoY | Look at last year's same period |
Step 9 — Generate review report
# Product Metrics Review
**Period:** {date range}
**Product:** {name}
**Type:** {weekly / monthly / quarterly}
## 1. Health Overview
| Layer | Metric | Current | Previous | MoM | Target | Status |
|---|---|---|---|---|---|---|
| North Star | {} | {} | {} | {±X%} | {} | OK / warn / alert |
| L1 | {} | {} | {} | {±X%} | {} | OK / warn / alert |
**Overall judgment:** {one-sentence summary}
## 2. User Growth
- DAU: {value}, MoM {change}
- MAU: {value}, DAU/MAU = {stickiness}
- Composition: new {X}% / retained {Y}% / returning {Z}%
## 3. Retention
| Metric | Current | Previous | Benchmark | Assessment |
|---|---|---|---|---|
## 4. Funnel
| Step | Users | Rate | MoM | Bottleneck? |
|---|---|---|---|---|
**Bottleneck diagnosis:** {description}
## 5. Experiments / Feature Effects
| Experiment | Primary metric Δ | Significance | Conclusion |
|---|---|---|---|
## 6. OKR Progress
| KR | Target | Current | Progress | Risk |
|---|---|---|---|---|
## 7. Anomaly Attribution
| Anomaly | Magnitude | Start | Attribution | Confidence |
|---|---|---|---|---|
## 8. Key Insights
1. {insight 1: finding + data + meaning}
2. {insight 2}
3. {insight 3}
## 9. Action Recommendations
| Priority | Action | Linked metric | Expected impact | Owner |
|---|---|---|---|---|
Review cadence
| Type | Frequency | Time | Audience | Focus |
|---|---|---|---|---|
| Weekly | Every Monday | 15-30 min | PM | NSM + anomalies + experiments |
| Monthly | Month start | 30-60 min | Product team | All L1 + retention + funnel + OKR pacing |
| Quarterly | Quarter end | 60-90 min | Product + ops + eng | Strategy review + OKR scoring + next-quarter plan |
Quality bar
- Metric definitions clear — every metric has a calculation note
- Data has comparisons — current always compared to previous, YoY, or target
- Attribution evidenced — no causation from correlation alone
- Recommendations actionable — owner-assignable
- Limitations tagged — call out small samples or data quality issues
Common analysis pitfalls
| Pitfall | Symptom | Fix |
|---|---|---|
| Simpson's paradox | Total goes up while every segment goes down | Always segment, never just look at totals |
| Survivorship bias | Only retained users analyzed, churned ignored | C |
Content truncated.
When not to use it
- →When data is missing or lacks a baseline
- →When attempting to infer causation from correlation
Limitations
- →User-invoked only; do not auto-trigger
- →Requires baseline data for meaningful comparison
How it compares
It enforces a structured review process with specific benchmarks and data integrity checks, avoiding the pitfalls of analyzing vanity metrics or small fluctuations.
Compared to similar skills
pm-metrics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pm-metrics (this skill) | 0 | 1mo | No flags | Intermediate |
| quant-analyst | 103 | 2mo | No flags | Advanced |
| stock-analyzer | 71 | 1mo | Review | Beginner |
| xlsx | 87 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
quant-analyst
zenobi-us
Expert quantitative analyst specializing in financial modeling, algorithmic trading, and risk analytics. Masters statistical methods, derivatives pricing, and high-frequency trading with focus on mathematical rigor, performance optimization, and profitable strategy development.
stock-analyzer
FrancyJGLisboa
Provides comprehensive technical analysis for stocks and ETFs using RSI, MACD, Bollinger Bands, and other indicators. Activates when user requests stock analysis, technical indicators, trading signals, or market data for specific ticker symbols.
xlsx
anthropics
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
google-analytics
davila7
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user behavior, or performance optimization.
market-sizing-analysis
wshobson
This skill should be used when the user asks to "calculate TAM", "determine SAM", "estimate SOM", "size the market", "calculate market opportunity", "what's the total addressable market", or requests market sizing analysis for a startup or business opportunity.
data-engineering
pluginagentmarketplace
ETL pipelines, Apache Spark, data warehousing, and big data processing. Use for building data pipelines, processing large datasets, or data infrastructure.