startup-validator
Skill7 starsChanged 6 days agoMITView on GitHub
Validate a startup, product, or feature thesis with falsifiable customer, market, and economics evidence. Use for new venture ideas, pivots, ICP selection, pricing hypotheses, and go/no-go decisions.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- letscooktech-studio/ai-engineering-arsenalword for word, first seen Nov 8, 2026
- ggombee/code-forgetheir own version, first seen Apr 20, 2026
- FelipeAngeli/skillstheir own version, first seen Apr 10, 2026
- pedronauck/skillstheir own version, first seen Apr 3, 2026
- Vimalk0703/startup-validator-skilltheir own version, first seen Feb 26, 2026
Other versions5 projects use a version of this.
Word for word · 1
- letscooktech-studio/ai-engineering-arsenal★ 7100% same
Edited · 0
None found.
Wrote their own version · 4
- pedronauck/skills★ 649same name
- ggombee/code-forge★ 18same name
- FelipeAngeli/skills★ 2same name
- Vimalk0703/startup-validator-skill★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentic-skill-pack-integratorSkill
- ai-agent-architecture-reviewerSkill
- ai-search-optimizerSkill
- competitor-analyzerSkill
- cost-explosion-detectorSkill
- cto-operating-systemSkill
- database-architectSkill
- nextjs-production-architecture-reviewerSkill
- nvidia-accelerated-ai-systems-operatorSkill
- production-ai-saas-builderSkill
- production-risk-labSkill
- security-auditorSkill
- seo-auditorSkill
- supabase-production-auditorSkill
- system-architectSkill
- technical-debt-hunterSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Write a one-sentence falsifiable thesis: customer, painful job, measurable outcome, and willingness-to-pay condition.
- Distinctive: line 30
Do not treat TAM slides or survey intent as demand proof.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Startup Validator
Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.
Replace narrative confidence with a sequence of cheap, falsifiable tests.
Intake
Capture the proposed customer, painful job, current workaround, trigger event, solution, distribution route, constraints, and available evidence. Label statements as facts, assumptions, or guesses.
Workflow
- Write a one-sentence falsifiable thesis: customer, painful job, measurable outcome, and willingness-to-pay condition.
- Segment the market by urgency and access, then choose a beachhead ICP with a reachable interview list.
- Map alternatives including manual work, doing nothing, and incumbent products.
- Design evidence in ascending cost: desk research, problem interviews, concierge test, landing-page/offer test, and paid pilot.
- Define a pass/fail threshold before each test. Update confidence only from observed behavior, not compliments.
Output contract
Provide a thesis card, assumption ledger, competitor/alternative map, ranked experiments, interview guide, pricing test, and a go/pivot/stop recommendation. For every recommendation include the next observable signal and owner.
Quality gates
- Do not treat TAM slides or survey intent as demand proof.
- Require a clear status for desirability, viability, feasibility, and distribution.
- State sample bias, evidence age, and confidence intervals where relevant.
- Make the smallest next experiment capable of changing the decision.
Improvement loop
Log prediction versus result after every test; retire disproven assumptions and rerank the next uncertainty by decision impact.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

