Idea Validator

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

116 stars 35 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add aakashg/pm-claude-skills --skill idea-validator
Manual install
git clone --depth 1 https://github.com/aakashg/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/skills/idea-validator ~/.claude/skills/idea-validator

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Idea Validator

Stress-test a product idea across 5 dimensions and return a GO / ITERATE / STOP verdict with evidence.

## Step 0 — Read first

| Source | Path | What to extract |
|--------|------|-----------------|
| Project context | `CLAUDE.md` | Company, market, target users, current focus |
| Scoring rubric | `references/scoring-rubric.md` | Strong/Moderate/Weak bar for each dimension |
| User's materials | any doc, deck, or notes they name | Actual customer quotes, usage data, pricing research |
| Existing research | `docs/`, `research/` if present | Prior validation on the same problem |

If the user names no materials, say so explicitly in the verdict. An idea validated only against your training data is a hypothesis, not a validation, and you must label it that way.

## Constraints

Mandatory. These override the user's enthusiasm.

- Every rating requires 3–5 sentences of specific reasoning. A rating with no evidence is invalid.
- Never rate STRONG without a named comparable, a number, or a cited user behavior.
- Never default to GO because the user is excited. Honesty is the deliverable.
- Never treat "no competitors" as opportunity. It usually means no market. Say so.
- Never recommend "build the MVP" as the first next step.
- Flag every guess with `ASSUMPTION:` and name the data that would confirm or deny it.
- Flag every missing input with `[NEED: X]`.
- Never give all five STRONGs unless the evidence is genuinely exceptional. Most ideas are a mix.
Read the full skill on GitHub

Details

Skill name
idea-validator
Path
skills/idea-validator/SKILL.md
License
MIT
Repo updated
8 August 2026

FAQ

What does the Idea Validator skill do?

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

How do I install the Idea Validator skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add aakashg/pm-claude-skills --skill idea-validator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Idea Validator popular?

It lives in aakashg/pm-claude-skills, which has 116 GitHub stars and 35 forks.

Related skills

Linkedin Post Writer

116

aakashg/pm-claude-skills

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

Writing & Content35

Product Designer

116

aakashg/pm-claude-skills

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

Frontend & Design35

Prompt Engineer

116

aakashg/pm-claude-skills

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

AI, LLMs & Agents35

Test

155

serpro69/claude-toolbox

Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.

Testing & QAIn 1 list30

S4h Probability Confidence Calibration

242

human-avatar/skills-for-humanity

Tests whether stated confidence levels match available evidence — catching overconfidence and underconfidence. Use when asked to 'calibrate my confidence', 'am I overconfident', 'confidence check', 'how sure should I be', or 'is this as certain as it seems'.

Testing & QAIn 1 list25

Playwright E2E Tester

272

curiositech/some_claude_skills

Expert in end-to-end testing with Playwright, the modern cross-browser testing framework. Specializes in test generation, page object patterns, visual regression testing, and CI/CD integration. Handles complex testing scenarios including authentication flows, API mocking, and mobile emulation.

Testing & QA46

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.