Agent skill

Lean Startup

by wondelai in wondelai/skills

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn.

MITAuto-check passedBusiness, Finance & HR

Install Lean Startup

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

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

GitHub CLI
$ gh skill install wondelai/skills lean-startup --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-startup .claude/skills/lean-startup && 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-startup
GitHub stars
2.4k
Token cost
~4.2k tokens
SKILL.md length
2,005 words
Files
12 (incl. references)
Skills in repo
62
Repo updated
First seen
Licence
MIT

At a glance

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn.

  • Works in 6 steps: Establish the Baseline → Tune the Engine → Pivot or Persevere → …
  • The user mentions MVP scope
  • SKILL.md covers Core Principle, Scoring, The Build-Measure-Learn Loop and Validated Learning, plus 13 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lean Startup is an agent skill from wondelai/skills. Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change…

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/applications.md`, `references/assumptions.md` and `references/build-measure-learn.md`).

It sits in Business, Finance & HR, covering Accounting and bookkeeping and User stories. 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 MVP scope
  • Validated learning
  • Test assumptions
  • Innovation accounting

Example prompts

  • “MVP scope”
  • “validated learning”
  • “pivot or persevere”
  • “/lean-startup”

Workflow steps

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

  1. Establish the Baseline
  2. Tune the Engine
  3. Pivot or Persevere
  4. Sticky Engine of Growth
  5. Viral Engine of Growth
  6. Paid Engine of Growth

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 Startup loads about 4.2k tokens when it runs, and up to ~42k if it reads all its reference files. Until then it costs about 178 tokens; SKILL.md has 2,005 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~178
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
~42k

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,005 words, ~4,242 tokens.

Download SKILL.mdSave it as .claude/skills/lean-startup/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
lean-startup
description
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.
license
MIT
metadata.author
wondelai
metadata.version
1.4.0

Lean Startup Methodology

A systematic approach to building startups and launching new products that shortens development cycles and rapidly discovers whether a business model is viable.

Core Principle

Entrepreneurship is a form of management. Success doesn't require a perfect plan or brilliant insight—it requires a systematic process for testing assumptions, learning from customers, and iterating rapidly. Most startups fail not because they couldn't build what they planned, but because they built the wrong thing: treat every plan as a set of hypotheses to falsify, and spend effort to eliminate waste and accelerate validated learning, not to execute a fixed roadmap.

Scoring

Goal: 10/10. Score a plan, experiment, or metric set by the five Quick Diagnostic rows—1 point each when the answer is yes, 2 points when it is also backed by evidence on the Validation Ladder (Level 3+):

  • 9-10: every leap-of-faith assumption named and ranked by risk, the riskiest tested by a real MVP, actionable metrics defined, and explicit pivot criteria set before building.
  • 5-6: a hypothesis and some MVP exist, but metrics are vanity or pivot criteria are undefined—decisions can't be made from the data.
  • ≤3: waterfall thinking—building the full product first, asking customers what they want, or scaling before product/market fit.

State the current score and the lowest-scoring diagnostic row to fix next.

The Build-Measure-Learn Loop

The fundamental cycle: IDEAS → BUILD (product) → MEASURE (data) → LEARN (knowledge) → back to IDEAS.

Critical insight: Plan the loop backward:

  1. What do we want to learn? (hypothesis to test)
  2. How will we know if we learned it? (metrics)
  3. What's the minimum we can build? (MVP)

Goal: Minimize total time through the loop.

See references/build-measure-learn.md when planning an experiment—reverse-planning sequence, an experiment-design template, per-product-type loop examples, and the build/vanity-metric loop traps.

Validated Learning

Learning what customers really want through experiments on real behavior—not feature requests, surveys, or focus groups (people mispredict their own behavior). Measure what customers do, not what they say, and run experiments that could falsify your assumptions. Vanity wins (downloads, signups without engagement) are not learning.

The Validation Ladder:

LevelEvidenceStrength
1"I think customers want this"Weakest (opinion)
2"Customers said they want this"Weak (stated preference)
3"Customers signed up for early access"Medium (low commitment)
4"Customers paid a deposit"Strong (real commitment)
5"Customers are actively using it"Strongest (revealed preference)

Target: Level 4-5 before building at scale.

Minimum Viable Product (MVP)

The version of a new product that allows maximum validated learning with the least effort. Not a prototype (technical feasibility), not a beta (quality), not a minimum marketable product—a learning vehicle, often embarrassingly small and low quality, and usually much smaller than you think.

MVP Types:

TypeWhat It IsWhen to UseExample
ConciergeManual service pretending to be automatedTest if solution is valuableFood on the Table (manual meal planning)
Wizard of OzFake automation, manual backendTest if automation is neededZappos (no inventory, bought shoes retail)
Smoke testLanding page + signup, no productTest demand before buildingDropbox video (explained concept, measured signups)
Single featureOne core feature onlyTest which feature is most valuableTwitter (just status updates)
PiecemealCombine existing toolsTest workflow before custom buildGroupon (WordPress + email)

Design questions: What's the riskiest assumption? What's the minimum that tests it? How do we measure whether it was validated?

See references/mvp-design.md when choosing and sizing an MVP—seven types in depth, a type-selection decision matrix, lower/upper sizing bounds, and the MVP Design Canvas.

Leap-of-Faith Assumptions

The assumptions that, if wrong, will cause your business to fail. Identify them, prioritize by risk (which failure would be fatal?), and test the riskiest first—never in order of ease.

Assumption TypeQuestionTest Method
Value hypothesisDo customers care about this problem?Smoke test, concierge MVP
Growth hypothesisHow will customers discover us?Channel tests, referral experiments
Retention hypothesisWill customers come back?Cohort analysis, engagement metrics
Monetization hypothesisWill customers pay?Pre-orders, pricing tests

Example—Dropbox: Leap of faith: "people will download and use a file sync tool." Test: explainer video before building scale infrastructure. Result: beta list grew from 5,000 to 75,000 overnight—demand validated.

See references/assumptions.md when mapping and ranking assumptions—the Impact-Uncertainty matrix, a prioritization scoring template, test methods per assumption type, and industry-specific assumption lists.

Innovation Accounting

Measuring progress when traditional metrics fail: revenue and customers start at zero, and vanity metrics look good without driving decisions.

1. Establish the Baseline

Measure current reality precisely, even if it's zero or embarrassing: conversion funnel (signup → active → retained → paying), engagement (DAU/MAU, session length, features used), economics (CAC, LTV, churn).

2. Tune the Engine

Run experiments to improve baseline metrics: A/B test pricing ($9 vs. $19/mo), onboarding completion rates, acquisition channels (SEO vs. paid vs. referral). Each experiment targets a measurable improvement through validated learning.

3. Pivot or Persevere

When tuning stalls, make the evidence-based call (criteria and pivot types below in Pivot or Persevere).

See references/innovation-accounting.md when building the baseline dashboard—funnel, cohort, and economics metric frameworks.

Actionable vs. Vanity Metrics

Vanity metrics make you feel good but don't change behavior; actionable metrics drive decisions and clarify cause and effect.

VanityWhy It's BadActionable Alternative
Total signupsAlways goes up, no context% signup → active (conversion rate)
Page viewsDoesn't indicate valueTime on page, bounce rate
Total usersIncludes inactive/churnedActive users (DAU, WAU, MAU)
DownloadsDoesn't mean usageDAU/downloads (activation rate)
RevenueWithout contextRevenue per cohort, LTV/CAC

Three characteristics of actionable metrics: actionable (clear cause-and-effect, reproducible), accessible (simple, understood by everyone), auditable (underlying data can be checked).

Example: Vanity: "We have 100,000 users!" Actionable: "Channel X users retain 2x better than channel Y—double down on X."

Cohort analysis: Group users by signup date and track behavior over time—the only way to see whether the product is actually improving.

See references/metrics.md when building a cohort table or choosing what to track—a five-step cohort walkthrough and AARRR (Pirate Metrics) aligned with Lean Startup stages.

Pivot or Persevere

A pivot is a structured course correction designed to test a new hypothesis about the product, strategy, or engine of growth.

Pivot when: experiments repeatedly fail to validate hypotheses, metrics stay flat despite iterations, customer feedback contradicts the vision, or progress is too slow for the runway. Persevere when: metrics are improving (even slowly), clear learning is happening, and adjustments move the right direction.

Pivot Types:

Pivot TypeWhat ChangesExample
Zoom-inSingle feature becomes the whole productInstagram (photo filters from Burbn)
Zoom-outProduct becomes a single featureFlickr (photo-sharing from Game Neverending)
Customer segmentSame problem, different customerGroupon (activism platform → local deals)
Customer needSame customer, different problemPotbelly (antique store → sandwiches)
PlatformApp ↔ PlatformYouTube (dating site → video platform)
Business architectureHigh margin/low volume ↔ low margin/high volumeSalesforce (software → SaaS)
Value captureMonetization model changeAndroid (paid → free + app revenue)
Engine of growthViral, sticky, or paid modelFacebook (viral in colleges → paid advertising)
ChannelHow you reach customersSalesforce (direct sales → self-service)
TechnologyDifferent technology, same solutionApple (Intel → ARM chips)

Cadence: Successful startups commonly pivot 1-5 times before product-market fit. Anti-pattern: "pivoting" without validating that the new direction solves the core problem.

See references/pivots.md when the data suggests a pivot—the data-driven pivot signals, a structured pivot-meeting agenda, leading indicators, and the Instagram/Slack/YouTube pivot stories.

Show full SKILL.md (797 more words)Show less

The Three Engines of Growth

How a startup acquires and retains customers sustainably. Pick one engine, optimize it, then consider adding others—running multiple engines simultaneously dilutes focus and learning.

1. Sticky Engine of Growth

Retention-driven: growth rate = new customer acquisition rate − churn rate. Track churn rate, retention cohorts (30/60/90 days), and DAU/MAU. Fits SaaS, subscriptions, social networks. Strategy: improve the product until natural growth exceeds churn.

2. Viral Engine of Growth

Customers bring customers: viral coefficient = (% who invite) × (invites sent) × (% who join); above 1.0 means exponential, self-sustaining growth. Track the coefficient, viral cycle time, and referral attribution. Fits Dropbox, Hotmail, WhatsApp. Strategy: build virality into the product itself.

3. Paid Engine of Growth

Spend to acquire: requires LTV > CAC (target LTV/CAC > 3x). Track CAC, LTV, and payback period. Fits e-commerce and traditional businesses. Strategy: optimize until each customer's profit funds acquiring more.

See references/growth-engines.md when picking or tuning an engine—churn-reduction tactics, the K-factor and viral-loop design, LTV/CAC optimization, a channel-economics table, and the product-to-engine matching framework.

The Five Whys

Root cause analysis: when a problem occurs, ask "why?" five times, then invest proportionally at every level—not just the symptom.

Example—website went down:

  1. Why? Server ran out of memory
  2. Why? Memory leak in a new feature
  3. Why? Code wasn't reviewed for memory management
  4. Why? No code review process for infrastructure changes
  5. Why? Team is moving too fast to create processes

Proportional investments: fix the bug (1), add memory monitoring (2), implement code review (3-4), slow down to build quality processes (5). Anti-pattern: stopping at level 1.

See references/five-whys.md when facilitating a session—three worked examples (outage, churn spike, launch failure) and how to handle diverging chains, blame creep, and root causes outside your control.

Small Batches

Work in small batches for faster feedback loops, easier pivots, less waste when you're wrong, and faster time to market.

Large BatchSmall Batch
Build entire product, then launchLaunch landing page, then build
Release quarterlyRelease weekly or daily
Plan 12-month roadmapPlan 6-week cycles
Big bang rewriteIncremental refactoring

Continuous deployment is the ultimate small batch: deploy every commit, catch bugs immediately, learn continuously, reduce risk per release.

See references/small-batches.md when setting up faster release cadence—the continuous-deployment pipeline and prerequisites, feature-flag types, a progressive-rollout checklist, and work-decomposition techniques.

Lean Startup Applied: From Idea to Scale

Phase 1—Problem/Solution Fit: validate that the problem exists and customers care, via customer discovery, smoke tests, and concierge MVPs. Metric: customers willing to pay or commit.

Phase 2—Product/Market Fit: build the MVP and iterate on usage data. Metric: high retention, organic growth, strong engagement.

Phase 3—Scale: optimize the growth engine and unit economics. Metric: sustainable, profitable growth. Anti-pattern: skipping Phases 1-2 and jumping straight to scale.

By context:

  • SaaS startup: smoke test (landing page + email list) → concierge MVP with 10 customers → single-feature MVP → measure retention, NPS, feature usage → pivot or scale on cohort data
  • Corporate innovation: separate innovation accounting from core-business metrics, shield teams from quarterly revenue pressure, unlock metered funding on validated-learning milestones
  • Product features: deploy behind a feature flag → A/B test against core metrics → kill, iterate, or scale based on data

See references/applications.md for context-specific playbooks (SaaS, corporate innovation, features), and references/case-studies.md for the full Dropbox, IMVU, Zappos, and Groupon stories—including failures—when you want a worked precedent for the bet in front of you.

Common Mistakes

MistakeWhy It FailsFix
Building too muchWaste before validationTest with smoke test or concierge first
Asking customersPeople don't know/mispredictObserve behavior, not opinions
Vanity metricsFeel-good numbers, no decisionsTrack cohorts, conversion, retention
No hypothesisCan't learn if you don't predictWrite hypothesis before each experiment
Pivot too slowWaste runwaySet clear pivot criteria upfront
Skip innovation accountingCan't tell if you're improvingEstablish baseline, measure tuning efforts
Premature scale optimizationPolishing before product-market fitValidate learning first; quality follows evidence

Quick Diagnostic

Audit any product development plan:

QuestionIf NoAction
What's the riskiest assumption?Building on shaky groundMap leap-of-faith assumptions
How will you test it?You're guessingDesign MVP to test the assumption
What metric will validate/invalidate?You won't learnDefine actionable metrics
Can you test with less than this?Over-buildingShrink the MVP further
What will you do if the experiment fails?No pivot criteriaDefine pivot triggers upfront

Further Reading

For the complete framework, research, and case studies:

About the Author

Eric Ries is an entrepreneur and author who developed the Lean Startup methodology as co-founder and CTO of IMVU, where he pioneered the continuous deployment and customer development practices behind it. The Lean Startup has been translated into over 30 languages and shaped startup culture worldwide. He later created the Long-Term Stock Exchange (LTSE).

© 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 11 other files (references) in lean-startup of wondelai/skills.

  • SKILL.md
  • references/applications.md
  • references/assumptions.md
  • references/build-measure-learn.md
  • references/case-studies.md
  • references/five-whys.md
  • references/growth-engines.md
  • references/innovation-accounting.md
  • references/metrics.md
  • references/mvp-design.md
  • references/pivots.md
  • references/small-batches.md

Open the folder on GitHubat commit c172996

Compare with similar skills

Lean Startup 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 Startup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lean Startup this skillwondelai/skills2.4k—~4.2kAutomated safety check: PassMIT
Discovery Draftingdanjdewhurst/story-skills2831 repos~2kAutomated safety check: NotesMIT
Lean Startupgetagentseal/founder-playbook729—~4.6kAutomated safety check: PassMIT
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence
ERPClaw ERP Controlleravansaber/erpclaw114—~18kAutomated safety check: PassGPL-3.0

Similar skills

  • Discovery Drafting

    danjdewhurst/story-skills

    This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead…

    283 GitHub starsUsed in 1 repo~2k tokens
    Business, Finance & HRAuto-check: notes
  • Lean Startup

    getagentseal/founder-playbook

    Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.

    729 GitHub stars~4.6k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 7 days ago
    Business, Finance & HRAuto-check passed
  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 18 days ago
    Business, Finance & HRAuto-check passed
  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    114 GitHub stars~18k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    421 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from wondelai/skills

All 62 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 29 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 29 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 29 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 29 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 29 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 29 days ago
    Auto-check passed

Questions about Lean Startup

What does Lean Startup do?

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Lean Startup is an agent skill from wondelai/skills. Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn.

When should I use Lean Startup?

Lean Startup fits situations like: the user mentions MVP scope; validated learning; test assumptions; innovation accounting.

How do I install Lean Startup in Claude Code?

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

How do I install Lean Startup in Codex?

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

Can I use Lean Startup 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-startup -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-startup, .gemini/skills/lean-startup, .github/skills/lean-startup and .opencode/skills/lean-startup in your project.

What does Lean Startup need to run?

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

Does Lean Startup 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 Startup 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 Startup use?

Lean Startup 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 Startup 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 37k tokens, read only when the agent opens those files.

What are the alternatives to Lean Startup?

Skills that share tags, products or a category with Lean Startup: Discovery Drafting (danjdewhurst/story-skills, 283 stars), Lean Startup (getagentseal/founder-playbook, 729 stars), Sync Upstream (nyaruka/phonenumbers, 1.6k stars) and Radiology Table (huang-sir1/radiology-skills, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lean Startup?

wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,362 GitHub stars. The repository holds 62 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.