SkillAgentSearch skills...

lean-analytics

Choose and audit startup metrics using Croll and Yoskovitz''s "Lean Analytics"

Install / Use

npx skills add wondelai/skills --skill lean-analytics

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Universal

Tags

Our assessment of lean-analytics

lean-analytics scores 84/100 on our quality scale, 476th of 606 Data & Analytics skills we index.

Its SKILL.md is 17 KB long, well organised into 13 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
12/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so lean-analytics is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

lean-analytics compared with similar skills

All 4 of these similar skills score higher than lean-analytics; compare them before choosing.

SkillScoreStarsUpdatedFormat
lean-analytics (this skill)by wondelai842.2k2mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install lean-analytics?
Run npx skills add wondelai/skills --skill lean-analytics. The install tabs above show the steps for each supported agent.
Which AI agents does lean-analytics work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is lean-analytics safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is lean-analytics still maintained?
The repository was last updated about 2 months ago, so lean-analytics is actively maintained.

name: lean-analytics description: 'Choose and audit startup metrics using Croll and Yoskovitz''s "Lean Analytics". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters (OMTM)", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing a dashboard for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers good-vs-vanity metrics, the One Metric That Matters, metrics by business model, the five startup stages, and benchmarks. For the build-measure-learn loop, see lean-startup. For fixing activation and retention, see improve-retention.' license: MIT metadata: author: wondelai version: "1.2.0"

Lean Analytics

A data discipline for startups distilled from Alistair Croll and Benjamin Yoskovitz's Lean Analytics: separate metrics that change decisions from numbers that merely flatter, then point the whole company at the One Metric That Matters for your business model and stage. Use it to choose metrics, audit dashboards, set targets, and plan instrumentation.

Core Principle

Focus on the one metric that matters right now — everything else is noise that feels like progress. Startups die from lack of focus more often than lack of data. The discipline is knowing your business model, knowing your stage, and tracking the single number that tells you whether the riskiest part of the business is working. A metric earns attention only if it changes what you do next.

Scoring

Goal: 10/10. Rate metric choices, dashboards, and instrumentation plans 0-10 against these principles. Report the current score and the specific changes needed to reach 10/10.

  • 9-10: One OMTM matched to model and stage, paired counter-metric, a line in the sand with a pre-committed miss response, cohorted and segmented data
  • 7-8: Mostly actionable ratios and a plausible OMTM, but no explicit target, weak cohorting, or too many "key" metrics
  • 5-6: Actionable and vanity metrics mixed; dashboard exists but rarely changes a decision; model and stage never named
  • 3-4: Vanity metrics dominate — totals, cumulative charts, blended averages; metrics copied from other companies
  • 0-2: No instrumentation, or numbers chosen to impress investors rather than drive decisions

Framework

1. Good Metrics vs Vanity Metrics

Core concept: A good metric is comparative (versus last week, versus another cohort), understandable (the team can recall and debate it), a ratio or rate (not an ever-growing total), and behavior-changing — if a number won't change what you do, stop measuring it. Vanity metrics — total signups, page views, cumulative anything — only go up and only make you feel good.

Why it works: The output of analytics is decisions, not data. Ratios are inherently comparative and operable, while totals hide decay: total registered users rises even while the product bleeds actives. Forcing every metric through the "what will we do differently?" test converts reporting into learning.

Key insights:

  • Work the lens pairs: qualitative vs quantitative (interviews reveal why, numbers reveal how much), exploratory vs reporting (exploration finds your unfair advantage; reporting keeps the lights on), leading vs lagging (complaints predict churn before churn happens), correlated vs causal
  • Correlation finds the lever; only an experiment proves it — find metrics that move together, then change one for a randomized group to test causality
  • Cohorts make time honest: compare users by signup month, or real improvement vanishes inside blended averages
  • Segments make comparisons honest: split by channel, plan, and geography — a flat aggregate often hides one segment soaring and another collapsing
  • Averages lie under skew: whales and lurkers are different businesses, so read medians and percentiles
  • A cumulative up-and-to-the-right chart is the single most reliable vanity tell

Applications:

| Context | Application | Example | |---------|-------------|---------| | Dashboard audit | Rewrite each total as a ratio | Total signups → % of visitors activating within 7 days | | Board reporting | Show cohorts, not cumulative curves | Retention by signup month replaces "users over time" | | Feature decision | Demand a behavior-changing metric | "If D7 retention doesn't rise 10%, the feature comes out" |

See references/good-metrics.md when auditing a dashboard or running a metric through the four tests — full test definitions, the 10-row vanity rewrite table, a worked cohort-retention example, segmentation rules, the correlation-to-causation experiment loop, and a metric-definition template.

2. The One Metric That Matters (OMTM)

Core concept: At any moment there is one number that matters above all others — the one that tells you whether the current riskiest assumption is working. Pick it, display it everywhere, and let it drive every experiment until you graduate to the next stage.

Why it works: The OMTM answers the most important question you have right now, forces you to draw a line in the sand so "good" is defined before results arrive, and focuses the entire company. A dashboard of forty numbers diffuses accountability; one number creates a shared scoreboard and a culture of experimentation.

Key insights:

  • The OMTM rotates — it is the metric that matters now, not forever; passing a stage gate or pivoting changes it
  • Pair it with a counter-metric so it can't be gamed: activation speed paired with 30-day retention, sales velocity paired with refund rate
  • A line in the sand has three parts: a target number, a date, and a pre-committed answer to "what do we do if we miss?"
  • "Good enough" is a decision made in advance, not a discovery made after — otherwise the goalposts move
  • If the team can't agree on the OMTM, you haven't agreed what the riskiest part of the business is — that argument is the valuable part
  • Collect many metrics, but watch one — the rest live in drill-down reports, not on the wall

Applications:

| Context | Application | Example | |---------|-------------|---------| | Quarterly planning | One OMTM per stage; experiments ladder up to it | Stickiness stage → all bets target week-4 retention | | Dashboard design | OMTM big, 4-6 supporting metrics small | Wall display: paid conversion 3.2% huge; CAC, churn, NPS below | | Team alignment | Pre-commit the miss response | "Under 10% by March 1 → we pivot to the agency segment" |

Ethical boundary: The line in the sand disciplines the company's bets, not individuals — turning the OMTM into personal quotas invites gaming and hides truth.

See references/omtm.md when choosing or rotating the OMTM, pairing a counter-metric, or drawing the line in the sand — the six-step selection procedure, the 6x3 stage x model matrix, a 7-row counter-metric gaming table, line-in-the-sand and rotation-trigger rules, and three worked examples.

3. Metrics by Business Model

Core concept: Your business model dictates which metrics exist and which matter. Lean Analytics defines six archetypes — e-commerce, SaaS, free mobile app, media site, user-generated content, and two-sided marketplace — each with its own metric tree and its own definition of "working."

Why it works: Copying another company's north star fails because metrics encode the mechanics of a model: a marketplace lives or dies on liquidity, a SaaS business on churn, a media site on engaged attention. Naming your model first turns "what should we measure?" from a brainstorm into a lookup.

Key insights:

  • E-commerce runs on conversion rate, average order value, and repurchase rate — annual repurchase under ~40% means acquisition mode, over ~60% loyalty mode, and each mode has a different playbook
  • SaaS runs on MRR, churn, LTV:CAC, expansion, and time-to-value; free mobile apps run on downloads → DAU/MAU, percent paying, and ARPDAU vs ARPPU (whales skew every average)
  • Media runs on audience, engaged time (not raw pageviews), CTR, and RPM; UGC runs on the engagement funnel — visitor → voyeur → commenter → creator — plus content per user and spam rate
  • Marketplaces run on liquidity: listings, fill/sell-through rate, time-to-transaction, take rate, buyer/seller ratio — GMV is vanity until multiplied by take rate
  • Hybrid businesses must pick ONE primary model to own the OMTM; the secondary model contributes counter-metrics, not equal billing
  • The model also dictates instrumentation: define each metric's formula and source up front, or every team computes "churn" differently

Applications:

| Context | Application | Example | |---------|-------------|---------| | New product instrumentation | Name the model, install its metric tree | Subscription box → primary model SaaS; churn tracked before AOV | | North-star debate | Derive from model mechanics, don't copy | Marketplace adopts fill rate, not a SaaS-style MRR target | | Investor dashboard | Report the model's canonical ratios | SaaS deck: MRR growth, net churn, LTV:CAC, CAC payback |

See references/business-model-metrics.md when instrumenting a product or picking a model's canonical ratios — metric trees for all six models with formulas, instrumentation notes, measurement failure modes, and hybrid-model guidance.

4. Metrics by Stage: The Lean Analytics Stages

Core concept: Startups move through five stages — Empathy, Stickiness, Virality, Revenue, Scale — and each has a gate. The OMTM is the intersection of business model and current stage; working on a later stage's metric before passing the current gate is the canonical startup mistake.

Why it works: Sequencing prevents waste. Virality poured into a product that doesn't retain is a leaky bucket; paid acquisition before unit economics burns runway with precision. Each gate de-risks the next, larger investment of money and time.

Key insights:

  • Empathy: have 15+ problem interviews shown a painful, frequent problem people will pay to fix? The metric is mostly conversation notes — and that's correct at this stage
  • Stickiness: do people use it repeatedly on their own? Track retention cohorts and core-action engagement; don't pour users into a leaky bucket
  • Virality: do users bring users? Track viral coefficient AND cycle time — shortening the cycle often grows you faster than raising the coefficient, and inherent virality beats incentivized invites
  • Revenue: does a dollar in return more than a dollar out, soon enough? Revenue per customer, CAC payback, gross margin
  • Scale: channels, partners, and new markets — metrics shift from product risk to ecosystem and operations
  • Gates are evidence, not time: a flattening retention curve exits Stickiness; positive unit economics within payback tolerance exits Revenue

Applications:

| Context | Application | Example | |---------|-------------|---------| | Growth-spend decision | Check the stickiness gate first | D30 retention at 4% → fix onboarding before buying ads | | Roadmap prioritization | Stage picks the OMTM; OMTM picks the work | Stickiness stage ships onboarding fixes, not a referral program | | Fundraising narrative | Pitch the passed gate and its evidence | "Week-4 retention flat at 35% — raising to scale acquisition" |

See references/five-stages.md when locating your stage or deciding whether you've passed a gate — the per-stage playbook with gating metrics, exit-criteria checklists, premature-scaling symptoms, and funding/runway interactions.

5. Baselines and Lines in the Sand

Core concept: A metric without a target is trivia. Use published baselines as starting heuristics — not laws — to define "good enough," then draw your line in the sand: a number, a date, and a pre-committed action if you miss.

Why it works: Baselines convert open-ended measurement into falsifiable bets

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryData
Updated2mo ago
Forks228

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions