agentsclimarketplace

Idea validator

Skill tuliosousapro/SaaS-blueprint/skills/idea-validator

Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.From its SKILL.md

Install
npx -y skills add tuliosousapro/SaaS-blueprint --skill idea-validator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 4 commands, including `firecrawl_search: "{problem_statement} pain point frustrated"` and 3 more.

SKILL.md

4.4 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Idea Validator Skill

When to Use

  • After completing Phase 0 (Idea) before entering Phase 1 (Validation)
  • When the user proposes a new idea or pivot
  • When deciding between multiple product directions
  • As a sanity check before committing resources

Tools Required

ToolPurpose
firecrawl_searchValidate market signals, demand indicators
firecrawl_extractPull data from market reports, forums

Instructions

1. Collect Idea Inputs

Get from the user (or from completed Phase 0 deliverables):

  • Problem statement: What pain does this solve?
  • Target user: Who has this pain? (be specific: role, company size, industry)
  • Proposed solution: How does this solve it? (one sentence)
  • Revenue model: How does this make money?
  • Differentiator: Why can't they just use {existing solution}?

2. Score on 5 Dimensions

Each dimension scored 1-5. Total score determines recommendation.

A. Problem Severity (1-5)

ScoreCriteria
1Nice-to-have. Users tolerate current solutions fine.
2Mild annoyance. Users complain but don't switch.
3Real pain. Users actively search for alternatives.
4Hair-on-fire. Users lose money/time daily without a solution.
5Mission-critical. Business cannot function without solving this.

Validate with:

firecrawl_search: "{problem_statement} pain point frustrated"
firecrawl_search: "site:reddit.com {target_user} struggling with {problem}"

B. Willingness to Pay (1-5)

ScoreCriteria
1Users expect free. No existing paid solutions.
2Users pay reluctantly. < $10/mo willingness.
3Established paid market. $10-50/mo common.
4Users budget for this. $50-200/mo normal.
5Enterprise budgets. $200+/mo, multi-seat deals.

Validate with:

firecrawl_search: "{category} pricing SaaS"
firecrawl_search: "{competitor} pricing plans"

C. Market Timing (1-5)

ScoreCriteria
1Market is saturated or declining.
2Market exists but growth is flat.
3Growing market with room for new entrants.
4Emerging market with strong tailwinds (AI, regulation, etc.).
5Category creation opportunity — no one owns this yet.

D. Founder-Market Fit (1-5)

ScoreCriteria
1No domain expertise, no network, no unfair advantage.
2Some interest but learning from scratch.
3Adjacent experience. Understand the user but not the domain deeply.
4Direct experience. Have felt this pain personally.
5Deep domain expertise + network + distribution advantage.

E. Execution Feasibility (1-5)

ScoreCriteria
1Requires team of 10+, $1M+, regulatory approval.
2Needs specialized skills the founder lacks.
3Achievable solo with AI tools in 3-6 months.
4MVP shippable in 30-60 days with existing tools.
5Can validate in a weekend with no-code or AI agents.

3. Generate Scorecard

# Idea Validation Scorecard: {Idea Name}

| Dimension | Score | Evidence |
|-----------|-------|----------|
| Problem Severity | X/5 | {one-line justification} |
| Willingness to Pay | X/5 | {one-line justification} |
| Market Timing | X/5 | {one-line justification} |
| Founder-Market Fit | X/5 | {one-line justification} |
| Execution Feasibility | X/5 | {one-line justification} |
| **TOTAL** | **XX/25** | |

## Recommendation
- 20-25: **STRONG GO** — Execute immediately.
- 15-19: **CONDITIONAL GO** — Proceed but validate {weakest dimension} first.
- 10-14: **PAUSE** — Significant risks. Pivot or de-risk before investing.
- 5-9:  **NO GO** — Fundamental problems. Explore different ideas.

4. Risk Flags

Regardless of score, flag these as deal-breakers:

  • Problem Severity = 1 → "No one needs this"
  • Willingness to Pay = 1 → "Can't monetize"
  • Execution Feasibility = 1 → "Can't build it"

5. Output Format

Save to BRAINIAC/0. Idea/VALIDATION_SCORECARD.md

Quality Gates

  • Every score must have evidence (search result, data point, or user testimony)
  • WTP score must reference actual competitor pricing
  • Total recommendation must match the scoring bands exactly

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in ~1.1k tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Collect problem statement and target user details
  • Score problem severity from one to five
  • Score willingness to pay from one to five
  • Score market timing from one to five
  • Score founder market fit from one to five
  • Score execution feasibility from one to five

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.