Agent skill

Lean Analytics

by wondelai in wondelai/skills

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

MITAuto-check passedProduct & Project Management

Install Lean Analytics

skills CLI
$ npx skills add wondelai/skills --skill lean-analytics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wondelai/skills lean-analytics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/lean-analytics .claude/skills/lean-analytics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lean-analytics
GitHub stars
2.4k
Token cost
~4.2k tokens
SKILL.md length
2,266 words
Files
6 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Good Metrics vs Vanity Metrics → The One Metric That Matters (OMTM) → Metrics by Business Model → …
  • The user mentions what metrics should we track
  • SKILL.md covers Core Principle, Scoring, Framework and Common Mistakes, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lean Analytics is an agent skill from wondelai/skills. 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…

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/business-model-metrics.md`, `references/case-studies.md` and `references/five-stages.md`).

It sits in Product & Project Management, covering Product strategy, OKRs and executive reporting and Product metrics. The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.

When your agent uses it

  • The user mentions what metrics should we track
  • North star metric
  • One Metric That Matters (OMTM)
  • Analytics dashboard

Example prompts

  • “Lean Analytics”
  • “what metrics should we track”
  • “north star metric”
  • “/lean-analytics”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Good Metrics vs Vanity Metrics
  2. The One Metric That Matters (OMTM)
  3. Metrics by Business Model
  4. Metrics by Stage: The Lean Analytics Stages
  5. Baselines and Lines in the Sand

What it can do on your machine

Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • amazon.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lean Analytics loads about 4.2k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 189 tokens; SKILL.md has 2,266 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~189
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~21k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 2,266 words, ~4,235 tokens.

Download SKILL.mdSave it as .claude/skills/lean-analytics/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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
metadata.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:

ContextApplicationExample
Dashboard auditRewrite each total as a ratioTotal signups → % of visitors activating within 7 days
Board reportingShow cohorts, not cumulative curvesRetention by signup month replaces "users over time"
Feature decisionDemand 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:

ContextApplicationExample
Quarterly planningOne OMTM per stage; experiments ladder up to itStickiness stage → all bets target week-4 retention
Dashboard designOMTM big, 4-6 supporting metrics smallWall display: paid conversion 3.2% huge; CAC, churn, NPS below
Team alignmentPre-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:

ContextApplicationExample
New product instrumentationName the model, install its metric treeSubscription box → primary model SaaS; churn tracked before AOV
North-star debateDerive from model mechanics, don't copyMarketplace adopts fill rate, not a SaaS-style MRR target
Investor dashboardReport the model's canonical ratiosSaaS 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.

Show full SKILL.md (1,023 more words)Show less
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:

ContextApplicationExample
Growth-spend decisionCheck the stickiness gate firstD30 retention at 4% → fix onboarding before buying ads
Roadmap prioritizationStage picks the OMTM; OMTM picks the workStickiness stage ships onboarding fixes, not a referral program
Fundraising narrativePitch 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. Knowing that ~5% monthly churn is the early-SaaS ceiling tells you whether to optimize or rebuild; without a line, every result can be rationalized and no experiment can fail.

Key insights:

  • Early SaaS: ~5% monthly customer churn is the upper bound of viable; healthy companies push toward ~2% or lower
  • Habitual and social apps: DAU/MAU around 20%+ signals real engagement; casual mobile apps average roughly 14% day-30 retention, so plan for steep decay
  • Conversion: e-commerce typically converts ~1-3% of visitors; landing pages on good paid traffic usually convert low single digits — 25-30% is exceptional, not a planning number
  • A viral coefficient above 1 is rare and fleeting; treat virality as CAC reduction and optimize cycle time before coefficient
  • No benchmark for your case? Measure your current value, improve relative to it, and watch the derivative — 5% weekly improvement compounds into category-leading numbers
  • Benchmarks shift by market, channel, price point, and era — always re-derive against your own cohorts before adopting someone else's number

Applications:

ContextApplicationExample
Target settingBaseline → line in the sand → pre-commitment"Churn under 4% by Q3 or we rebuild onboarding"
Anomaly triageCompare to your own baseline before benchmarksConversion fell 2.4% → 1.9% in a week — investigate the release
Channel evaluationRe-derive benchmarks per channelPaid social converts 0.8%, search 4% — budget follows the line

See references/case-studies.md when you want a full worked walkthrough — three scenarios: SaaS dashboard to OMTM, marketplace liquidity discovery, and a mobile app fixing stickiness before growth.

Common Mistakes

MistakeWhy It FailsFix
A dashboard with 40 metricsDiffuses focus; nobody owns anythingOne OMTM big, 4-6 supporting metrics, archive the rest
Celebrating cumulative chartsTotals can't go down, so they hide decayPlot rates, conversions, and cohort retention instead
Copying another company's north starMetrics encode model mechanics you don't shareDerive the OMTM from your model × stage
Skipping cohortsBlended averages mask whether the product improvesTrack each signup cohort separately over time
Optimizing virality before stickinessGrowth multiplies churn — the leaky bucketPass the retention gate, then build invite loops
Measuring what's easy, not what's riskyDecisions still get made on gutInstrument the riskiest assumption first
No line in the sandEvery result gets rationalized; experiments can't failPre-commit target, date, and miss response
Confusing correlation with causationYou pump a metric that doesn't drive the outcomeRun a controlled experiment before investing

Quick Diagnostic

QuestionIf NoAction
Can you name your OMTM right now?Focus is diffused across a dashboardPick one metric from current model × stage
Would this metric change what you do next?You're reporting, not decidingDrop it, or define the decision it gates
Is it a ratio or rate, not a total?Vanity risk — totals only go upRewrite as a conversion, retention, or per-user rate
Do you know your business model archetype?Wrong metric tree installedName one of the six models; adopt its metrics
Do you know your stage (Empathy → Scale)?Probably optimizing a later stage too earlyFind the first unpassed gate; that's your stage
Is there a target with a date and a miss plan?Goalposts will move after resultsDraw the line in the sand in writing
Is the data cohorted and segmented?Averages are hiding the truthBuild cohort tables; split by channel and segment
Is a counter-metric guarding the OMTM?The OMTM will be gamedPair it, e.g. signup growth × 30-day retention

Further Reading

About the Authors

Alistair Croll is an entrepreneur and analyst who co-founded web performance company Coradiant, founded Solve For Interesting, and chairs Startupfest among other technology conferences. Benjamin Yoskovitz is a founding partner at venture studio Highline Beta and a serial founder and startup investor. They wrote Lean Analytics for Eric Ries's Lean Series.

© wondelai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in lean-analytics of wondelai/skills.

  • SKILL.md
  • references/business-model-metrics.md
  • references/case-studies.md
  • references/five-stages.md
  • references/good-metrics.md
  • references/omtm.md

Open the folder on GitHubat commit c172996

Compare with similar skills

Lean Analytics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lean Analytics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lean Analytics this skillwondelai/skills2.4k—~4.2kAutomated safety check: PassMIT
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
Team OKR Brainstormphuryn/pm-skills27k—~1.1kAutomated safety check: PassMIT
AI Product Strategy InterviewerPrepLabsAI/InterviewMentor112—~4.5kAutomated safety check: PassMIT
Bmad Product Briefaj-geddes/claude-code-bmad-skills487—~1.7kAutomated safety check: NotesCustom licence
SaaS Revenue and Growth Metricsdeanpeters/Product-Manager-Skills7.2k1 repos~5.8kAutomated safety check: PassCustom licence

Similar skills

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Product & Project ManagementAuto-check passed
  • Team OKR Brainstorm

    phuryn/pm-skills

    Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.

    27k GitHub stars~1.1k tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed
  • AI Product Strategy Interviewer

    PrepLabsAI/InterviewMentor

    A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.

    112 GitHub stars~4.5k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Bmad Product Brief

    aj-geddes/claude-code-bmad-skills

    Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method.

    487 GitHub stars~1.7k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes
  • SaaS Revenue and Growth Metrics

    deanpeters/Product-Manager-Skills

    Explains and calculates SaaS revenue, retention and growth metrics such as MRR, ARPU, GRR and NRR, to read momentum, churn and product-market-fit signals.

    7.2k GitHub starsUsed in 1 repo~5.8k tokens
    Product & Project ManagementAuto-check passed
  • Designs a product metrics dashboard: a North Star and input metrics, a definition table with data sources, chart types and alert thresholds, and a screen layout.

    27k GitHub stars~1.3k tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed

More from wondelai/skills

All 61 skills in this repo
  • Crossing The Chasm

    wondelai/skills

    Navigate the technology adoption lifecycle from early adopters to mainstream market.

    2.4k GitHub stars~3.6k tokensUpdated 27 days ago
    Auto-check passed
  • Design Everyday Things

    wondelai/skills

    Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.

    2.4k GitHub stars~4k tokensUpdated 27 days ago
    Auto-check passed
  • Design Sprint

    wondelai/skills

    Run a structured 5-day process to prototype, test, and validate product ideas with real users.

    2.4k GitHub stars~3.8k tokensUpdated 27 days ago
    Auto-check passed
  • Hooked UX

    wondelai/skills

    Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).

    2.4k GitHub stars~3.5k tokensUpdated 27 days ago
    Auto-check passed
  • Improve Retention

    wondelai/skills

    Diagnose and fix retention problems using behavior design (B=MAP).

    2.4k GitHub stars~3.8k tokensUpdated 27 days ago
    Auto-check passed
  • Monetizing Innovation

    wondelai/skills

    Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".

    2.4k GitHub stars~5.2k tokensUpdated 27 days ago
    Auto-check passed

Questions about Lean Analytics

What does Lean Analytics do?

Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics". Lean Analytics is an agent skill from wondelai/skills. Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics".

When should I use Lean Analytics?

Lean Analytics fits situations like: the user mentions what metrics should we track; north star metric; one Metric That Matters (OMTM); analytics dashboard.

How do I install Lean Analytics in Claude Code?

Run `npx skills add wondelai/skills --skill lean-analytics -a claude-code`. Or copy the skill folder (lean-analytics in wondelai/skills) into .claude/skills/lean-analytics in your project. Claude Code loads it when a task matches its description.

How do I install Lean Analytics in Codex?

Run `npx skills add wondelai/skills --skill lean-analytics -a codex`. Or copy the skill folder (lean-analytics in wondelai/skills) into .agents/skills/lean-analytics in your project. Codex loads it when a task matches its description.

Can I use Lean Analytics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wondelai/skills --skill lean-analytics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lean-analytics, .gemini/skills/lean-analytics, .github/skills/lean-analytics and .opencode/skills/lean-analytics in your project.

What does Lean Analytics need to run?

SKILL.md names no scripts, command-line tools or credentials: Lean Analytics is instructions for the agent only.

Does Lean Analytics access the network?

SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.

Is Lean Analytics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lean Analytics use?

Lean Analytics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lean Analytics use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Lean Analytics?

Skills that share tags, products or a category with Lean Analytics: Product Strategist (alirezarezvani/claude-skills, 28k stars), Team OKR Brainstorm (phuryn/pm-skills, 27k stars), AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars) and Bmad Product Brief (aj-geddes/claude-code-bmad-skills, 487 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lean Analytics?

wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,356 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 10, 2026.

Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.