analyze-metrics
Analyze product metrics and identify trends when the user asks to review metrics, analyze KPIs, or assess product health
npx skills add majiayu000/claude-skill-registry --skill analyze-metrics --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyze Metrics ## Overview Review product metrics against targets, identify trends across cohorts, distinguish leading from lagging indicators, and generate hypotheses for unexpected changes. Turns raw numbers into actionable insight. ## Workflow 1. **Read metrics context** — Scan `.chalk/docs/product/` for any metrics framework, KPI definitions, or previous metrics reviews. Identify which metrics have defined targets and baselines. 2. **Gather metrics data** — Parse `$ARGUMENTS` for the specific metrics or period to analyze. If the user provides data inline or references a file, read it. If no data is provided, ask the user to supply current metric values. 3. **Classify each metric** — For each metric, determine: - Type: leading (predictive) vs. lagging (outcome) - Category: acquisition, activation, engagement, retention, revenue, referral - Comparison basis: target value, previous period, cohort benchmark 4. **Assess current vs. target** — Compare each metric's current value against its target. Classify as: on-track (within 10%), at-risk (10-25% off), or off-track (>25% off). If no target exists, note the gap. 5. **Identify trends** — For each metric with historical data, clas
- Overview
- Workflow
- Output
- Anti-patterns
What does the analyze-metrics skill do?
Analyze product metrics and identify trends when the user asks to review metrics, analyze KPIs, or assess product health
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyze-metrics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.