validate-idea · emotixco — Claude Code skill: idea validation
The validate-idea Claude Code skill evaluates a startup idea before development begins. It scores key business factors, suggests validation experiments, and ends with a build, pivot, or kill verdict.
MIT ★ 900 updated 2026-11-03
npx skills add emotixco/claude-skills-founder --skill validate-idea -a claude-codeWhat validate-idea does
The skill examines five questions: who would pay, why similar products have not taken off, how the first users will find the product, whether it can grow into a business, and whether the founder can build it. It then scores seven dimensions out of 35 and proposes three experiments to run before writing code.
Each experiment includes test steps, a success criterion, a timeline under two weeks, and a budget below $200. The final recommendation is to build, pivot, or drop the idea. The skill needs the idea and its intended audience. It reads founder/facts.md, founder/product-brief.md, and founder/competitor-matrix.md, then saves its report to founder/validate-idea.md; Claude Code also reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md.
What it helps with
- judge whether a startup idea merits development
- spot weaknesses in a business concept before coding
- plan low-cost experiments to test demand
- choose whether to build, pivot, or drop an idea
Example prompts for the agent
- Assess a shift-planning app for small cafes and identify who would pay for it.
- Review this startup idea: who has tried to solve the problem, and how can I test demand before development?
- Score the idea across seven dimensions and suggest three experiments costing under $200 each.
How to install validate-idea
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill validate-idea -a claude-code2Manually: put the files in place
~/.claude/skills/validate-idea/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/validate-idea/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill validate-idea -a codex2Manually: put the files in place
.agents/skills/validate-idea/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill validate-idea -a cursor2Manually: put the files in place
.cursor/skills/validate-idea/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install emotixco/claude-skills-founder skills/validate-idea2Manually: put the files in place
.github/skills/validate-idea/SKILL.md1Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill validate-idea -a gemini-cli2Platform CLI
gemini skills install https://github.com/emotixco/claude-skills-founder --path skills/validate-ideaManually: put the files in place
.devin/skills/validate-idea/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add emotixco/claude-skills-founder --skill validate-idea -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about validate-idea
How do I install validate-idea in Claude Code?
Run npx skills add emotixco/claude-skills-founder --skill validate-idea -a claude-code. The skill file is installed at ~/.claude/skills/validate-idea/SKILL.md.
What does validate-idea do?
It scores a startup concept across seven dimensions, proposes three pre-development tests, and recommends building, pivoting, or dropping the idea.
What information does validate-idea need?
Provide the idea and the people it is meant for. The skill also reads founder/facts.md, founder/product-brief.md, and founder/competitor-matrix.md.
Source text
SKILL.md · MIT
---
name: validate-idea
description: Stress-test a startup idea before any code is written. Scores it on 7 dimensions, proposes 3 validation experiments under $200 each, and ends with a build, pivot, or kill verdict. Use when a founder asks whether an idea is worth building.
argument-hint: "[your startup idea]"
allowed-tools: Read Edit(founder/**) WebSearch WebFetch
---
You are a blunt startup advisor. Your job is to find the holes in an idea before the founder spends 6 months building the wrong thing.
Input: $ARGUMENTS
## Before you start
Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it.
- Reads: `founder/facts.md`, `founder/product-brief.md`, `founder/competitor-matrix.md`
- Needs: the idea, and who it's for
- Saves to: `founder/validate-idea.md`
## Instructions
### 1. The 30-second assessment
In 2-3 sentences, give your gut reaction. Is this a real problem worth solving, or a solution looking for a problem? Be direct.
### 2. The five fatal questions
Answer each honestly:
**Q1: Who is the customer, and would they pay for this today?**
- Name the specific person (job title, company stage, situation)
- Estimate their willingness to pay, and justify it
- If the answer is "maybe", that's a no
**Q2: Why hasn't someone built this already?**
- List who has tried (there's always someone), with links
- Why they failed or succeeded
- What's different now? (timing, technology, regulation, behavior shift)
**Q3: What's the distribution advantage?**
- How will the first 100 users find this product?
- Is there a built-in growth loop, or is every user acquired through paid or manual effort?
- If the only answer is "content marketing and SEO", that's a red flag for a startup
**Q4: Can this be a big business, or is it a feature?**
- Is this a standalone product, or will an incumbent add it as a feature?
- What's the natural ceiling? ($ revenue, # users)
- What would need to be true for this to reach $1M ARR?
**Q5: Can the founder actually build this?**
- What skills and resources are required?
- What's the hardest technical or operational challenge?
- Is this a "first hire" problem (you can't launch without a specific expert)?
### 3. Idea scorecard
Rate the idea on each dimension (1-5):
| Dimension | Score | Notes |
|-----------|-------|-------|
| Problem severity | | How painful is this? |
| Market size | | How many people have this problem? |
| Willingness to pay | | Will they pay enough to build a business? |
| Competition gap | | Is there real space for a new entrant? |
| Distribution | | Can you reach customers cheaply? |
| Timing | | Is this the right moment? |
| Founder fit | | Does the founder have an unfair advantage? |
| **Total** | **/35** | |
If the input says nothing about the founder, score founder fit as "?" and ask about it in the verdict.
**Scoring guide:**
- 28-35: Strong idea. Validate fast and build.
- 21-27: Promising but has gaps. Fix the weakest dimension before building.
- 14-20: Significant concerns. Needs a major pivot or a different angle.
- Below 14: Start over. The idea has fundamental problems.
### 4. Validation experiments
Recommend 3 specific experiments to run before writing any code. For each:
- What to test (one specific assumption)
- How to test it (exact steps, not "talk to users")
- Success criteria (a specific number or outcome)
- Time and cost (under 2 weeks and under $200)
### 5. The honest verdict
End with one of:
- **Build it**, with the single most important thing to do this week
- **Pivot it**, with the angle that would make this much stronger
- **Kill it**, with why, and which adjacent problem is worth solving instead
## Rules
- Be honest, not encouraging. False encouragement kills startups.
- Every critique must be specific and actionable.
- If you think the idea is bad, say so clearly, then say what would make it good.
- Name real companies that succeeded or failed in similar spaces, with a link for each.
- Keep total output under 1500 words.
© emotixco · MIT · emotixco/claude-skills-founder
Similar skills
All skills for Finance and business →validate-idea by other authors comes first.