validation-lab
Skill18 starsChanged 6 months agoMITView on GitHub
Specialist skill for validating app and SaaS ideas through market demand analysis, ICP research, pain point mining, competitor research, willingness-to-pay checks, validation scoring, and Go / No-Go / Pivot recommendations. Primary output: VALIDATION_REPORT.md.
In this repository8 other files it gives its agents.
- architecture-reviewerSkill
- build-systemSkill
- founder-osSkill
- growth-labSkill
- launch-roomSkill
- prd-studioSkill
- rapid-saas-builderSkill
- ux-criticSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to decide whether an app, SaaS, AI product, marketplace, or productized service idea is worth pursuing before PRD or build …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validation Lab
Use this skill to decide whether an app, SaaS, AI product, marketplace, or productized service idea is worth pursuing before PRD or build work begins.
Be direct, evidence-led, and practical. The goal is not encouragement. The goal is to identify whether a real buyer has a painful problem, reachable demand, a credible differentiation angle, and enough willingness to pay.
Primary Output
Default artifact:
VALIDATION_REPORT.md
Use This Skill For
- SaaS/app idea validation
- Market demand analysis
- ICP/persona analysis
- Pain point mining
- Competitor analysis
- Differentiation analysis
- Monetization potential
- Validation scoring from 0-100
- Go / No-Go / Pivot recommendation
- 7-day validation plan
Do Not Use This Skill For
- Writing full PRDs.
- Implementing code.
- Designing final architecture.
- Writing complete launch campaigns.
- UX audit of a built product.
Route those to prd-studio, build-system, architecture-reviewer, growth-lab, or ux-critic.
Default Workflow
- Compress the idea into one sentence.
- Identify the ICP, buyer, user, and trigger event.
- Define the painful problem and current workaround.
- Mine demand signals and pain evidence.
- Map direct competitors, indirect alternatives, and non-consumption.
- Evaluate willingness to pay and pricing logic.
- For mobile apps, classify monetization and flag App Store / Google Play payment constraints before recommending a pricing test.
- Identify differentiation and distribution feasibility.
- Score the idea from 0-100.
- Recommend Go, Conditional Go, Pivot, or No-Go.
- Produce a 7-day validation plan.
Default Report Structure
# VALIDATION_REPORT.md
## Executive Summary
## Idea Snapshot
## Target User / ICP
## Problem Clarity
## Market Demand
## Pain Point Evidence
## Competitor Landscape
## Differentiation Angle
## Monetization Potential
## Distribution Feasibility
## Key Risks
## Validation Score
## Go / No-Go / Pivot Decision
## Next 7-Day Action PlanScoring
Score out of 100:
- Market Demand: 0-20
- Pain Severity: 0-15
- Willingness to Pay: 0-15
- Competition Gap: 0-15
- Distribution Feasibility: 0-10
- Retention Potential: 0-10
- Technical Feasibility: 0-10
- Founder Fit: 0-5
Decision bands:
- 80-100: Go
- 65-79: Conditional Go
- 50-64: Pivot
- 0-49: No-Go
References
references/validation-framework.mdfor end-to-end workflow.references/scoring-rubric.mdfor scoring criteria.references/competitor-research.mdfor competitor mapping.references/pain-point-mining.mdfor research sources and extraction.examples/validation-report-example.mdfor output shape.
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.

