agentleFS
darkweb19darkweb19/skills/product-analytics/SKILL.md

product-analytics

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

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

26 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use query-optimization, learnings and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ffsshhttiikkSkill

    query-optimization

    Database query optimization

    Also in 4 projects that use this

  • SossenbinderSkill

    learnings

    Extract non-obvious learnings from the current session and save them to auto memory. Use when the user wants to capture what was learned during a coding session.

    Also in 3 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 3 projects that use this

  • harrissohail6Skill

    database-design

    Database schema design and SQL best practices. Use when designing tables, writing queries, or optimizing database performance.

    Also in 3 projects that use this

  • attentiondotnetSkill

    animation-vocabulary

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    Also in 3 projects that use this

  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for:

    line 12
  2. Distinctive:

    Run cohort + retention analysis

    line 36
  3. Distinctive:

    Keep one owner per KPI.

    line 69
  4. Distinctive:

    Use cohort and segment filters by default.

    line 71
  5. Distinctive:

    Prefer comparable time windows (weekly vs weekly, monthly vs monthly).

    line 72

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-patternFix
Vanity metrics — tracking pageviews or total signups without activation contextAlways 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 screenExecutive layer: 5-7 metrics. Feature layer: per-feature only
No decision rule — tracking a KPI with no threshold or action planEvery KPI needs: target, threshold, owner, and "if below X, then Y"
Averaging across segments — reporting blended metrics that hide segment differencesAlways segment by cohort, plan tier, channel, or geography
Ignoring seasonality — comparing this week to last week without adjustingUse 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.