idea-validation
Skill1 starsChanged 5 months agoMITView on GitHub
Guide founders through validating startup ideas before building. Use when a founder says "I have an idea", "help me validate", "is this a good idea", "should I build this", "customer discovery", or asks about product-market fit, market sizing, or customer interviews. Covers problem discovery, customer interviews, market validation, and go/no-go decisions.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- AdeyStudios/skillstheir own version, first seen Nov 1, 2026
- kiku-jw/codex-skillstheir own version, first seen Jul 28, 2026
- RefoundAI/lenny-skillstheir own version, first seen Jul 15, 2026
- EmersonBraun/skillstheir own version, first seen Apr 6, 2026
- Yusong-Enceladus/claude-skillstheir own version, first seen Mar 18, 2026
- walternate/skillstheir own version, first seen Feb 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- RefoundAI/lenny-skills★ 1.3ksame name
- Yusong-Enceladus/claude-skills★ 8same name
- EmersonBraun/skills★ 4same name
- AdeyStudios/skills★ 1same name
- kiku-jw/codex-skills★ 0same name
- walternate/skills★ 0same 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- business-modelSkill
- customer-successSkill
- finance-accountingSkill
- founder-playbookSkill
- fundraisingSkill
- go-to-marketSkill
- growth-analyticsSkill
- legal-complianceSkill
- marketing-brandSkill
- operationsSkill
- productSkill
- salesSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
10
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 14
Ask: "Where are you in the journey?"
- Distinctive: line 48
Search Reddit, Twitter, Facebook groups, forums for:
- Distinctive: line 68
Look for patterns: "too complicated", "missing X feature" = your opening.
- Distinctive: line 75
Keep going until clear patterns emerge
- Distinctive: line 83
Look for these "lightbulb moments" from successful founders:
- Distinctive: line 93
The Mom Test: Don't ask "Would you use this?" — ask "How have you tried to solve this before?" Past behavior > future predictions.
- Distinctive: line 106
Nikita Bier principle: Do things that don't scale.
- Distinctive: line 109
Create page: "Finally, [solution] for [specific audience]"
- Distinctive: line 134
No unfair advantage identified
- Distinctive: line 137
Remember: If you have to ask "Do I have product-market fit?" — you don't.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Idea Validation
Guide founders from raw idea to validated hypothesis with confidence to commit or kill.
Workflow
1. Diagnose Stage
Ask: "Where are you in the journey?"
| Stage | Signals | Next Step |
| Raw idea | "I'm thinking about..." | → Go to Step 2 |
| Hypothesis | Has problem + solution defined | → Go to Step 3 |
| Interviewed | Talked to 5+ people | → Go to Step 4 |
| Testing | Has MVP/landing page | → Go to Step 5 |
2. Shape the Hypothesis
Help founder articulate three components (Kevin Hale/YC framework):
- Problem: What burning pain exists? Who has it?
- Solution: What's the experiment/MVP?
- Insight: Why will YOU win? (unfair advantage)
Unfair advantages to probe for:
- Founder-market fit (lived the problem, domain expertise)
- Market timing (20%+ annual growth)
- 10x better product possibility
- Built-in distribution/word-of-mouth
- Network effects potential
Output: One-sentence hypothesis in format:
"[Target customer] struggles with [problem] because [root cause]. We believe [solution] will work because [insight/unfair advantage]."
3. Validate the Problem
Quick Validation (60 min) — Tom Bilyeu Method
For rapid signal-checking before deep interviews:
Problem Hunt (15 min) Search Reddit, Twitter, Facebook groups, forums for:
- "Why is there no..."
- "I wish someone would make..."
- "I've tried 5 different solutions..."
- "Paying $X but it doesn't even..."
Collect 10 specific complaints. Can't find 10? Different problem.
Size Check (10 min) Google Trends + Keyword Planner:
- <1K monthly searches = Dead
- 1K-10K = Niche (can work)
- 10K-100K = Solid opportunity
- 100K+ = Major market
Competition Map (15 min) Find top 5 competitors. Check pricing pages + 1-star reviews.
- Pricing <$50/mo + bad reviews = struggling market
- Pricing $100+ with good reviews = profitable space
Look for patterns: "too complicated", "missing X feature" = your opening.
Deep Validation — Customer Interviews
How many conversations?
- B2C with uniform behavior: ~20 interviews
- B2B with varied buying patterns: 50+ interviews
- Keep going until clear patterns emerge
See references/interview-guide.md for question scripts and signal detection.
Critical rule: Anything short of "I want this!" is really "No thanks."
4. Assess Market Pull
Look for these "lightbulb moments" from successful founders:
| Signal | Strength | Example |
| Polite interest | ❌ Weak | "Sure, I'd check it out" |
| Unsolicited referrals | ✅ Strong | People you didn't talk to reach out |
| Interrupted pitch | ✅ Strong | "Wait, you can do WHAT?" |
| Pre-purchase on mockup | ✅ Strong | Signed customers from Figma prototype |
| Inbound after launch | ✅ Strong | 133 leads in 72 hours (Pinwheel) |
The Mom Test: Don't ask "Would you use this?" — ask "How have you tried to solve this before?" Past behavior > future predictions.
5. Test Before Building
Choose validation method based on idea type:
| Idea Type | Validation Method |
| B2B SaaS | Sell on mockups/Figma before code |
| Consumer app | Simulate populated experience in Figma |
| Marketplace | Validate BOTH sides separately |
| Dev tools | Leverage personal network first, then SEO content |
Nikita Bier principle: Do things that don't scale. Make it the BEST it could ever be manually. If it works, then automate. If you only launch the "scalable" version, you won't know if it failed due to concept or execution.
Landing page test (if applicable):
- Create page: "Finally, [solution] for [specific audience]"
- Run $20-50 in ads
- Conversion benchmarks:
- <1% = Kill immediately
- 2-5% = Test further
- 5%+ = Build immediately
6. Decision Checkpoint
GO Signals
- People reaching out unprompted
- Strong reactions in interviews ("I need this")
- Pre-sales or LOIs on mockups
- Clear pattern in 20+ conversations
- You have an unfair advantage
PIVOT Signals
- Adjacent problem keeps coming up
- Different customer segment more excited
- Core insight valid, solution wrong
KILL Signals
- Lukewarm reactions after 20+ interviews
- Have to "convince" people of the problem
- Can't find 10 complaints in 15 min searching
- No unfair advantage identified
- Market too small (<1K searches, <$1B TAM)
Remember: If you have to ask "Do I have product-market fit?" — you don't. When you have it, you know.
Common Traps
See references/traps.md for the 7 deadly traps and how to avoid them.
Reference Files
references/frameworks.md— All 5 validation frameworks in detailreferences/case-studies.md— 8 founder stories (Vanta, Flexport, etc.)references/interview-guide.md— Question scripts + what to listen forreferences/traps.md— 7 traps with detection and avoidance
Adapted from Linas Beliūnas's The One-Person Unicorn founder skill set.
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.

