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…
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn.
$ npx skills add wondelai/skills --skill lean-startup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wondelai/skills lean-startup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .claude/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wondelai/skills/tree/main/lean-startupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wondelai/skills --skill lean-startup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wondelai/skills lean-startup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/lean-startup .agents/skills/lean-startup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .agents/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill lean-startup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wondelai/skills lean-startup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/lean-startup .cursor/skills/lean-startup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .cursor/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wondelai/skills.git --path lean-startup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wondelai/skills --skill lean-startup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wondelai/skills lean-startup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/lean-startup .gemini/skills/lean-startup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .gemini/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wondelai/skills lean-startupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wondelai/skills --skill lean-startup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/lean-startup .github/skills/lean-startup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .github/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill lean-startup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wondelai/skills lean-startup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/lean-startup .opencode/skills/lean-startup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lean-startup" agent skill from https://github.com/wondelai/skills/tree/main/lean-startup into .opencode/skills/lean-startup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lean-startup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
lean-startupDesign 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. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
amazon.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 2,005 words, ~4,242 tokens.
.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.A systematic approach to building startups and launching new products that shortens development cycles and rapidly discovers whether a business model is viable.
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.
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+):
State the current score and the lowest-scoring diagnostic row to fix next.
The fundamental cycle: IDEAS → BUILD (product) → MEASURE (data) → LEARN (knowledge) → back to IDEAS.
Critical insight: Plan the loop backward:
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.
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:
| Level | Evidence | Strength |
|---|---|---|
| 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.
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:
| Type | What It Is | When to Use | Example |
|---|---|---|---|
| Concierge | Manual service pretending to be automated | Test if solution is valuable | Food on the Table (manual meal planning) |
| Wizard of Oz | Fake automation, manual backend | Test if automation is needed | Zappos (no inventory, bought shoes retail) |
| Smoke test | Landing page + signup, no product | Test demand before building | Dropbox video (explained concept, measured signups) |
| Single feature | One core feature only | Test which feature is most valuable | Twitter (just status updates) |
| Piecemeal | Combine existing tools | Test workflow before custom build | Groupon (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.
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 Type | Question | Test Method |
|---|---|---|
| Value hypothesis | Do customers care about this problem? | Smoke test, concierge MVP |
| Growth hypothesis | How will customers discover us? | Channel tests, referral experiments |
| Retention hypothesis | Will customers come back? | Cohort analysis, engagement metrics |
| Monetization hypothesis | Will 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.
Measuring progress when traditional metrics fail: revenue and customers start at zero, and vanity metrics look good without driving decisions.
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).
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.
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.
Vanity metrics make you feel good but don't change behavior; actionable metrics drive decisions and clarify cause and effect.
| Vanity | Why It's Bad | Actionable Alternative |
|---|---|---|
| Total signups | Always goes up, no context | % signup → active (conversion rate) |
| Page views | Doesn't indicate value | Time on page, bounce rate |
| Total users | Includes inactive/churned | Active users (DAU, WAU, MAU) |
| Downloads | Doesn't mean usage | DAU/downloads (activation rate) |
| Revenue | Without context | Revenue 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.
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 Type | What Changes | Example |
|---|---|---|
| Zoom-in | Single feature becomes the whole product | Instagram (photo filters from Burbn) |
| Zoom-out | Product becomes a single feature | Flickr (photo-sharing from Game Neverending) |
| Customer segment | Same problem, different customer | Groupon (activism platform → local deals) |
| Customer need | Same customer, different problem | Potbelly (antique store → sandwiches) |
| Platform | App ↔ Platform | YouTube (dating site → video platform) |
| Business architecture | High margin/low volume ↔ low margin/high volume | Salesforce (software → SaaS) |
| Value capture | Monetization model change | Android (paid → free + app revenue) |
| Engine of growth | Viral, sticky, or paid model | Facebook (viral in colleges → paid advertising) |
| Channel | How you reach customers | Salesforce (direct sales → self-service) |
| Technology | Different technology, same solution | Apple (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.
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.
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.
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.
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.
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:
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.
Work in small batches for faster feedback loops, easier pivots, less waste when you're wrong, and faster time to market.
| Large Batch | Small Batch |
|---|---|
| Build entire product, then launch | Launch landing page, then build |
| Release quarterly | Release weekly or daily |
| Plan 12-month roadmap | Plan 6-week cycles |
| Big bang rewrite | Incremental 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.
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:
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.
| Mistake | Why It Fails | Fix |
|---|---|---|
| Building too much | Waste before validation | Test with smoke test or concierge first |
| Asking customers | People don't know/mispredict | Observe behavior, not opinions |
| Vanity metrics | Feel-good numbers, no decisions | Track cohorts, conversion, retention |
| No hypothesis | Can't learn if you don't predict | Write hypothesis before each experiment |
| Pivot too slow | Waste runway | Set clear pivot criteria upfront |
| Skip innovation accounting | Can't tell if you're improving | Establish baseline, measure tuning efforts |
| Premature scale optimization | Polishing before product-market fit | Validate learning first; quality follows evidence |
Audit any product development plan:
| Question | If No | Action |
|---|---|---|
| What's the riskiest assumption? | Building on shaky ground | Map leap-of-faith assumptions |
| How will you test it? | You're guessing | Design MVP to test the assumption |
| What metric will validate/invalidate? | You won't learn | Define actionable metrics |
| Can you test with less than this? | Over-building | Shrink the MVP further |
| What will you do if the experiment fails? | No pivot criteria | Define pivot triggers upfront |
For the complete framework, research, and case studies:
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
SKILL.md and 11 other files (references) in lean-startup of wondelai/skills.
Open the folder on GitHubat commit c172996
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lean Startup this skillwondelai/skills | 2.4k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Discovery Draftingdanjdewhurst/story-skills | 283 | 1 repos | ~2k | Automated safety check: Notes | MIT | |
| Lean Startupgetagentseal/founder-playbook | 729 | — | ~4.6k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| ERPClaw ERP Controlleravansaber/erpclaw | 114 | — | ~18k | Automated safety check: Pass | GPL-3.0 |
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…
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
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.
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…
wondelai/skills
Navigate the technology adoption lifecycle from early adopters to mainstream market.
wondelai/skills
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
wondelai/skills
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).
wondelai/skills
Diagnose and fix retention problems using behavior design (B=MAP).
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
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.
Lean Startup fits situations like: the user mentions MVP scope; validated learning; test assumptions; innovation accounting.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Lean Startup is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.
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.
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.
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.
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.
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.