
Idea Validator
- 8 installs
- 33 repo stars
- Updated April 26, 2026
- bighardperson/computer-science-skills-collection
idea-validator is a Claude skill that assesses startup ideas using an Opportunity Memo framework and a Perceived Created Value (PCV) score to decide whether to build.
About
This skill assesses a startup idea before building using a structured Problem Assessment Matrix and a Perceived Created Value (PCV) score. A developer or founder uses it to judge problem-solution fit and whether an idea is worth pursuing. It supplies scoring rubrics and discovery questions and points to related market-sizing and ICP skills.
- Assesses startup ideas with a Problem Assessment Matrix and Perceived Created Value (PCV) score
- Uses Hexa's Opportunity Memo framework to decide whether to pursue an idea
- Provides discovery questions across problem, timing, and ICP
Idea Validator by the numbers
- 8 all-time installs (skills.sh)
- Ranked #2,242 of 3,280 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
idea-validator capabilities & compatibility
Free; a framework-driven assessment with no external services.
- Capabilities
- idea validation · market research · problem scoping
- Use cases
- research · planning
- Runs
- Runs locally
- Pricing
- Free
What idea-validator says it does
Rigorously assess startup ideas BEFORE building using structured validation
Validation = Opportunity Memo Assessment + Perceived Created Value (PCV) Score
npx skills add https://github.com/bighardperson/computer-science-skills-collection --skill idea-validatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8 |
|---|---|
| repo stars | ★ 33 |
| Last updated | April 26, 2026 |
| Repository | bighardperson/computer-science-skills-collection ↗ |
What it does
Score a startup idea's problem-solution fit and decide whether it is worth building.
Who is it for?
Founders and developers deciding whether a startup idea is worth building.
Skip if: Teams past validation who need to design or ship the product.
When should I use this skill?
Someone asks whether an idea is good, or says they want to build X without validation.
By the numbers
- 4-dimension PCV scoring
- PCV score range 0-24
- 4-row Problem Assessment Matrix
Files
Idea Validator - Startup Idea Assessment Framework
Rigorously assess startup ideas BEFORE building using structured validation—saving months of wasted effort on ideas that won't work.
Hexa's Principle: "You want to make something people want. But people don't always know what they want—so you need to understand what they actually need."
When This Activates
- User asks "is this a good idea"
- User says "I want to build X" without validation
- User asks "should I pursue this"
- User mentions a startup idea they're considering
- User wants to know if their idea is worth building
The Framework
Validation = Opportunity Memo Assessment + Perceived Created Value (PCV) Score
Problem Assessment Matrix
| Dimension | Rating | Impact |
|---|---|---|
| Frequency | [Daily/Weekly/Monthly] | High/Med/Low |
| Severity | [Critical/Important/Nice-to-have] | High/Med/Low |
| Awareness | [Actively seeking/Aware/Unaware] | High/Med/Low |
| Budget | [Has budget/Would find/No budget] | High/Med/Low |
Problem Score: 3-4 High = Strong. 1-2 = Weak. 0 = Not a real problem.
PCV Scoring (4 Dimensions)
Rate current solution problems + your improvement:
| Dimension | Current Problem | Your Improvement |
|---|---|---|
| Price | Not a problem / A problem / Serious | No diff / Some / Serious |
| Quality | Not a problem / A problem / Serious | No diff / Some / Serious |
| Performance | Not a problem / A problem / Serious | No diff / Some / Serious |
| Convenience | Not a problem / A problem / Serious | No diff / Some / Serious |
Scoring: a=0, b=1, c=3 points. Sum all 8 ratings.
| Score | Interpretation | Recommendation |
|---|---|---|
| 0-6 | Weak | Don't pursue |
| 7-12 | Moderate | Needs refinement |
| 13-18 | Strong | Worth pursuing |
| 19-24 | Exceptional | Build NOW |
Quick Discovery Questions
Problem Space:
1. What specific pain point does your ICP feel? 2. How do they currently solve this? 3. What's wrong with current solutions? 4. How often do they experience this pain? 5. What does this problem cost them?
Timing:
1. Why is NOW the right time? 2. What has changed recently? 3. What barriers existed before that are now gone?
ICP:
1. Company type, size, industry 2. Buyer vs. user role 3. What triggers them to seek a solution?
Integration
| Skill | When to Use |
|---|---|
market-sizer | After validation passes |
startup-icp-definer | Deep dive on customer |
mvp-architect | Scope the build |
leads-researcher | Find design partners |
---
For detailed execution workflow, output templates, and PCV calculations: references/full-guide.md
{
"name": "idea-validator",
"version": "1.0.0",
"description": "Use this skill when users need to validate a startup idea, assess problem-solution fit, evaluate mar",
"author": {
"name": "Ship Shit Dev",
"email": "hello@shipshit.dev",
"url": "https://github.com/shipshitdev"
},
"license": "MIT",
"skills": "."
}
Idea Validator - Full Guide
Complete guide to validating startup ideas using Hexa's Opportunity Memo framework and PCV methodology.
Step 1: Project Canvas (Executive Summary)
Ask the user:
Describe your idea in one sentence:
>
1. What problem are you solving?
2. Who has this problem?
3. What's your proposed solution?
4. Why you? (Why are you the right person to build this?)
One-Liner Template: "For [target customer] who [pain point], [Product Name] provides [solution] that [key benefit], unlike [alternatives] which [limitation]."
Step 2: Problem Space Deep Dive
Ask the user:
Tell me about the problem:
>
1. What is the specific pain point(s) your ICP feels?
2. How do they currently solve this problem?
3. What's wrong with the current solutions?
4. How often do they experience this pain?
5. What does this problem cost them?
Problem Assessment Matrix:
| Dimension | Current State | Impact |
|---|---|---|
| Frequency | [Daily/Weekly/Monthly/Yearly] | [High/Med/Low] |
| Severity | [Critical/Important/Nice-to-have] | [High/Med/Low] |
| Awareness | [Actively seeking/Aware/Unaware] | [High/Med/Low] |
| Budget | [Has budget/Would find budget/No budget] | [High/Med/Low] |
Problem Score: Count "High" ratings. 3-4 = Strong problem. 1-2 = Weak problem. 0 = Not a real problem.
Step 3: Context & Timing Analysis
Ask the user:
Why is NOW the right time for this solution?
>
1. What has changed recently that makes this possible/necessary?
2. What barriers existed before that are now gone?
3. What trends support this idea?
4. Why hasn't this been solved before?
5. What happens if they DON'T solve this in the next 12 months?
Timing Assessment:
| Factor | Evidence |
|---|---|
| Technology enablers | [What tech now exists?] |
| Market shifts | [What behavior has changed?] |
| Regulatory changes | [What's now allowed/required?] |
| Economic factors | [What budget/spending has shifted?] |
| Competitive vacuum | [Why hasn't this been built?] |
Step 4: ICP Definition
ICP Canvas:
┌─────────────────────────────────────────────────┐
│ IDEAL CUSTOMER PROFILE │
├─────────────────────────────────────────────────┤
│ Company: [Type, Size, Industry] │
│ Buyer: [Title, Role, Decision Authority] │
│ User: [Title, Daily workflow] │
│ Trigger: [What event creates urgency] │
│ Budget: [Who pays, typical spend range] │
│ Buying Center: [Who else influences decision] │
└─────────────────────────────────────────────────┘Step 5: Solution & Value Proposition
Value Proposition Framework:
| Element | Your Answer |
|---|---|
| For | [ICP description] |
| Who | [Key pain point] |
| Our product is | [Category] |
| That provides | [Key benefit] |
| Unlike | [Primary alternative] |
| We | [Key differentiator] |
Step 6: Competitive Landscape
Competitive Analysis:
| Competitor | Type | Strengths | Weaknesses | Your Advantage |
|---|---|---|---|---|
| [Name] | Direct | |||
| [Name] | Indirect | |||
| DIY/Manual | Alternative | |||
| Status Quo | Inaction |
Step 7: Perceived Created Value (PCV) Scoring
Phase 1: Interview 20 potential customers
- Ask open-ended questions about their problem
- Understand their current solutions
- Don't pitch your solution—listen
Phase 2: Assess Current Solution
| Dimension | Definition | Rating |
|---|---|---|
| Price | Cost of current solution | [a] Not a problem / [b] A problem / [c] Serious problem |
| Quality | Relevance, reliability, service | [a/b/c] |
| Performance | Speed, output, efficiency | [a/b/c] |
| Convenience | Usability, accessibility, ease | [a/b/c] |
Phase 3: Evaluate Your Solution
| Dimension | Your Improvement |
|---|---|
| Price | [a] No difference / [b] Some improvement / [c] Serious improvement |
| Quality | [a/b/c] |
| Performance | [a/b/c] |
| Convenience | [a/b/c] |
Phase 4: Calculate PCV Score
Scoring: a=0 points, b=1 point, c=3 points
Sum all 8 ratings (4 problem + 4 solution):
| Score | Interpretation | Recommendation |
|---|---|---|
| 0-3 | Weak opportunity | Don't pursue |
| 4-6 | Moderate opportunity | Needs work—pivot or refine |
| 7-9 | Strong opportunity | Worth pursuing with caution |
| 10-12 | Excellent opportunity | Green light—move fast |
| 13+ | Exceptional opportunity | Build NOW |
Step 8: Design Partner Validation
Design Partner Readiness:
| Criteria | Status |
|---|---|
| 3-5 identified potential customers | [Yes/No] |
| They've agreed to test early versions | [Yes/No] |
| They'll commit to regular feedback calls | [Yes/No] |
| They'll pay something (even discounted) | [Yes/No] |
| They have the problem acutely | [Yes/No] |
Score: 4-5 = Ready to build. 2-3 = Need more validation. 0-1 = Not ready.
Output Template
# Idea Validation Report: [Idea Name]
## Executive Summary
**One-Liner:** [For X who Y, Product provides Z]
**PCV Score:** X/24
**Recommendation:** [Don't pursue / Needs work / Worth pursuing / Green light]
**Confidence Level:** [Low/Medium/High]
## Problem Assessment
### The Problem
[Description]
### Problem Score: X/4
| Dimension | Rating | Evidence |
|-----------|--------|----------|
| Frequency | [High/Med/Low] | [Why] |
| Severity | [High/Med/Low] | [Why] |
| Awareness | [High/Med/Low] | [Why] |
| Budget | [High/Med/Low] | [Why] |
## PCV Score Breakdown
### Current Solution Problems (Customer's Pain)
| Dimension | Rating | Points |
|-----------|--------|--------|
| Price | [a/b/c] | [0/1/3] |
| Quality | [a/b/c] | [0/1/3] |
| Performance | [a/b/c] | [0/1/3] |
| Convenience | [a/b/c] | [0/1/3] |
| **Subtotal** | | **X/12** |
### Your Solution Improvement
| Dimension | Rating | Points |
|-----------|--------|--------|
| Price | [a/b/c] | [0/1/3] |
| Quality | [a/b/c] | [0/1/3] |
| Performance | [a/b/c] | [0/1/3] |
| Convenience | [a/b/c] | [0/1/3] |
| **Subtotal** | | **X/12** |
### **Total PCV Score: X/24**
## Validation Next Steps
### If Score < 7
- [ ] Interview 10 more potential customers
- [ ] Identify what you got wrong about the problem
- [ ] Consider pivoting
### If Score 7-12
- [ ] Double down on customer interviews
- [ ] Refine value proposition
- [ ] Find 3 design partners before building
### If Score 13+
- [ ] Lock in 3-5 design partners
- [ ] Use `market-sizer` to size the opportunity
- [ ] Start building within 2 weeks
## Final Recommendation
**Verdict:** [Don't pursue / Pivot / Proceed with caution / Full speed ahead]
**If proceeding, first priority:** [Single most important next action]The 20-Interview Rule
Before declaring an idea validated:
1. Talk to 20 potential customers (not friends, not family) 2. Ask about their problem (not your solution) 3. Understand how they solve it today 4. Learn what they'd pay for a better solution 5. Get 3-5 to commit as design partners
If you can't find 20 people to interview, the market might not exist.
Common Mistakes to Avoid
1. Confirmation bias: Only talking to people who agree with you 2. Solution-first thinking: Falling in love with solution before validating problem 3. Fake validation: Counting "that's cool" as validation (it's not) 4. Too broad ICP: "Everyone" is not a customer segment 5. Skipping competition: Assuming no competition means opportunity 6. Ignoring timing: Good idea at wrong time = failed startup 7. No design partners: Building before anyone commits to use it 8. Vanity validation: Surveys instead of real conversations
Related skills
FAQ
What score means an idea is worth pursuing?
A PCV score of 13-18 is rated Strong (worth pursuing) and 19-24 is Exceptional (build now).
When does this skill run?
Before building, to assess whether the idea is worth the effort.