idea-validator
Skill0 starsChanged 7 months agoMITView on GitHub
Use when the user wants to validate a startup, app, SaaS, marketplace, creator, or product idea and says "validate my idea," "is this a good startup idea," "stress test this," "should I build this," "critique my idea," "tear apart this idea," or "is there a real business here.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- luongnv89/skillstheir own version, first seen Nov 6, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- PyDaft/idea-validator-skilltheir own version, first seen Nov 1, 2026
- hongphuc5497/skillstheir own version, first seen Nov 1, 2026
- jaredhhawk/claude-skillstheir own version, first seen Oct 25, 2026
- ziho7/idea-validatortheir own version, first seen Oct 11, 2026
Used with
Projects with it also use prd-generator and prompt-engineer.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dhzrxSkillprd-generator
Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products
Also in 3 projects that use this
JeffallanSkillprompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON/function-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Mathews-Tom/armory★ 340same name
- luongnv89/skills★ 145same name
- aakashg/pm-claude-skills★ 106same name
- HK-hub/AgentSkills★ 6same name
- patonkikh/APES★ 3same name
- dipaulavs/ClaudeCode-Workspace-2025★ 2same name
- hongphuc5497/skills★ 2same name
- dersi3/idea-validator-skill★ 0same name
- jaredhhawk/claude-skills★ 0same name
- PyDaft/idea-validator-skill★ 0same name
1 more not listed
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 repository4 other files it gives its agents.
- debug-detectiveSkill
- hook-writerSkill
- risk-calculatorSkill
- terms-decoderSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 101
Treat Competition Density as favorable only when the market is fragmented or underserved.
- Distinctive: line 102
Always give the three strongest arguments against the idea with no softening.
- Distinctive: line 105
Use numeric pass and fail signals whenever possible.
- Distinctive: line 106
If the idea is missing an ICP or business model, infer cautiously and say the inference explicitly.
- Very specific: line 107
Do not recommend building when Willingness to Pay or Distribution Path scores 1 unless the user is intentionally building a hobby project.
“Common” is measured: kept by at least 6 in 10 of the 10 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 Validator
Output Format
IDEA VALIDATION REPORT
--------------------------------------------------
Idea: [one-line description]
Target customer: [ICP]
Problem statement: [pain in one sentence]
SIX-DIMENSION SCORE
Problem Clarity: [1-5]
Market Size: [1-5]
Willingness to Pay: [1-5]
Competition Density: [1-5]
Founder-Market Fit: [1-5]
Distribution Path: [1-5]
Total: [0-30]
Score band: [KILL / ITERATE / BUILD / MOVE FAST]
SCORE READ
Strongest dimension: [dimension]
Weakest dimension: [dimension]
DEVIL'S ADVOCATE
1. [hard argument against the idea]
2. [hard argument against the idea]
3. [hard argument against the idea]
RISKIEST ASSUMPTION
Assumption: [single make-or-break belief]
Test under 2 weeks: [specific action]
Budget cap: [$0-$100]
Pass signal: [numeric threshold]
Fail signal: [numeric threshold]
VERDICT
[KILL / PIVOT / VALIDATE FIRST / BUILD]
Rationale: [direct explanation]Scoring Rubric
SCORING SCALE
1 = weak / unclear / unattractive
3 = workable but unproven
5 = strong and clearly evidenced
DIMENSIONS
Problem Clarity 1 vague or nice-to-have
3 recurring pain with partial urgency
5 sharp, frequent, expensive pain
Market Size 1 tiny or shrinking niche
3 viable niche with room for a small business
5 large or expanding market with many reachable buyers
Willingness to Pay 1 users expect free
3 some segment will pay if ROI is clear
5 clear budget owner and painful status quo
Competition Density 1 crowded with entrenched winners
3 mixed market, some whitespace
5 fragmented or underserved market
Founder-Market Fit 1 no insight, access, or credibility
3 some relevant exposure
5 deep lived pain, network, or proven edge
Distribution Path 1 no credible go-to-market path
3 one plausible but unproven channel
5 repeatable low-cost path to customersThresholds
THRESHOLDS
< 15 = KILL
15 - 22 = ITERATE
23 - 28 = BUILD
29 - 30 = MOVE FAST
VERDICT MAPPING
KILL -> verdict usually KILL
ITERATE -> verdict usually PIVOT or VALIDATE FIRST
BUILD -> verdict usually BUILD
MOVE FAST -> verdict BUILD with urgencyRULES
- Score each dimension from 1 to 5 with real justification, not optimism.
- Treat
Competition Densityas favorable only when the market is fragmented or underserved; crowded red oceans score low. - Always give the three strongest arguments against the idea with no softening.
- Name exactly one riskiest assumption, not a list.
- The test plan must be executable in under 2 weeks for under $100.
- Use numeric pass and fail signals whenever possible.
- If the idea is missing an ICP or business model, infer cautiously and say the inference explicitly.
- Do not recommend building when
Willingness to PayorDistribution Pathscores 1 unless the user is intentionally building a hobby project. VALIDATE FIRSTis the default verdict when the score lands inITERATEand the core assumption can be tested cheaply.
EXAMPLE TRIGGER PHRASES
- "validate my idea: AI scheduling for plumbers"
- "is this a good startup idea?"
- "stress test this marketplace concept"
- "should I build this SaaS for agencies?"
- "critique my idea with no sugarcoating"
- "tear apart this app concept"
- "is there a real business here or not?"
Analysis Sequence
1. State the idea, ICP, and pain in one line each.
2. Score all six dimensions.
3. Sum the score and label the score band.
4. Write the 3 strongest arguments against the idea.
5. Identify the single riskiest assumption.
6. Design the cheapest credible test under 2 weeks / under $100.
7. Output the verdict: KILL, PIVOT, VALIDATE FIRST, or BUILD.This skill is part of the NOUMENON Indie Founder Pack — gumroad.com/noumenon-ai
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.

