Percerno Skillsbeta
← everything it can do · product

Product Analytics TEXT

Defines product KPIs and metric frameworks (AARRR, North Star, HEART) tailored to product stages, designs dashboard hierarchies, and performs cohort, retention, and funnel analysis to interpret feature adoption and user behavior trends.

0 uses this weeksource alirezarezvanilicence MIT
Not measured yet. Every skill is tested against the bare model on its own example requests; results appear here.
Security scan: clean · 2026-10-24 · 4 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Hjælp mig med at definere de vigtigste KPI'er for vores produkt, som netop har fundet product-market fit.”
“Kør en kohorteanalyse på denne events.csv-fil og vis mig retentionsmatricen for månedlige kohorter.”
“Vi har for mange metrikker på vores dashboard. Kan du hjælpe mig med at strukturere det i et executive-lag og et produkt-sundheds-lag?”
“Define the top 5 KPIs for our SaaS product which is currently in the growth stage.”
“I have a CSV of user events. Run a cohort analysis to see how retention changes for users who signed up in January vs February.”
“Help me structure a dashboard for the executive team. We need 5-7 directional metrics that show overall product health.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

product-kpiscohort-analysisretentionmetric-dashboardfunnel-analysisaarrnorth-star-metricfeature-adoption

Not for

Do not use this skill for financial SaaS metrics like ARR, MRR, or LTV calculation, which require the `finance/saas-metrics-coach` skill. It is also not for designing A/B tests or statistical significance testing, which should be handled by `product-team/experiment-designer`.

Details

When it is the right choice

Use this skill when you need to define or refine product metrics for a specific stage of the product lifecycle (pre-PMF, growth, or mature). It is appropriate for designing executive or product health dashboards, running cohort and retention analyses on event data, and interpreting feature adoption trends to identify drop-off points or success signals.

The full recipe the assistant reads

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
  2. AARRR for growth loops and funnel visibility
  3. North Star for cross-functional strategic alignment

  4. HEART for UX quality and user experience measurement

  5. Define stage-appropriate KPIs

  6. Pre-PMF: activation, early retention, qualitative success
  7. Growth: acquisition efficiency, expansion, conversion velocity

  8. Mature: retention depth, revenue quality, operational efficiency

  9. Design dashboard layers

  10. Executive layer: 5-7 directional metrics
  11. Product health layer: acquisition, activation, retention, engagement

  12. Feature layer: adoption, depth, repeat usage, outcome correlation

  13. Run cohort + retention analysis

  14. Segment by signup cohort or feature exposure cohort
  15. Compare retention curves, not single-point snapshots

  16. Identify inflection points around onboarding and first value moment

  17. Interpret and act

  18. Connect metric movement to product changes and release timeline
  19. Distinguish signal from noise using period-over-period context
  20. 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)
Files in this skill (5)
  • LICENSE
  • SKILL.md
  • references/dashboard-templates.md
  • references/metrics-frameworks.md
  • scripts/metrics_calculator.py
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path product-team/skills/product-analytics, licence MIT. The upstream licence file ships inside the skill.