solo-validate
Score startup idea through S.E.E.D. niche check + STREAM 6-layer analysis + Devil's Advocate inversion, auto-pick stack, and generate PRD with acceptance criteria. Use when user says "validate idea", "score this idea", "should I build this", "go or kill", "generate PRD", or "evaluate opportunity". Do NOT use for deep research (use /research first) or decision-only framework (use /stream).
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/fortunto2/solo-validate/validate
Validate a startup idea end-to-end: search KB, run Manifest alignment, S.E.E.D. niche check, Devil's Advocate inversion, STREAM 6-layer analysis, pick stack, generate PRD.
Philosophy: Validation should be honest, not optimistic. Better to kill a bad idea in 5 minutes than waste 3 months building it. The goal is truth, not encouragement.
MCP Tools (use if available)
If MCP tools are available, prefer them over CLI:
kb_search(query, n_results)— search knowledge base for related docsproject_info()— list active projects with stacksweb_search(query)— search for dead startups, competitor failures
If MCP tools are not available, fall back to Grep/Glob/WebSearch.
Steps
-
Parse the idea from
$ARGUMENTS. If empty, ask the user what idea they want to validate. -
Search for related knowledge: If MCP
kb_searchtool is available, use it directly:kb_search(query="<idea keywords>", n_results=5)Otherwise search locally:- Grep for idea keywords in
.mdfiles across the project and knowledge base Summarize any related documents found (existing ideas, frameworks, opportunities).
-
Deep research (optional): Check if
research.mdexists for this idea (look indocs/or the current working directory).- If it exists: read it and use findings to inform STREAM analysis and PRD filling (competitors, pain points, market size).
- If it does not exist: ask the user if they want to run deep research first. If yes, tell them to run
/research <idea>and come back. If no, continue without it.
-
Manifest Alignment Check (with teeth):
Consult
references/manifest-checklist.md(bundled with this skill) for the full checklist of 9 principles and 6 red flags. Check the idea against EACH one. This is not a formality — a manifest violation is a soft kill flag.For each principle, assess: comply or violate? If violating — cite the specific principle.
Key principles (see checklist for details):
- Privacy-first / offline-first
- One pain -> one feature -> launch
- AI as foundation, not feature
- Speed over perfection (MVP in days)
- Antifragile architecture
- Money without overheating
- Against exploitation
- Subscription fatigue
- Creators, not robots
Scoring: 0 violations = perfect, 1-2 = caution, 3+ = strong KILL signal.
Be honest. If the idea conflicts with principles, SAY SO. Don't rationalize alignment.
-
S.E.E.D. niche check (quick, before deep analysis):
Score the idea on four dimensions:
- S — Searchability: Can you rank? Forums/Reddit in top-10, few fresh giants, no video blocks?
- E — Evidence: Real pain with real quotes/URLs? Or hypothetical?
- E — Ease: MVP in 1-2 days on existing stack? No heavy dependencies?
- D — Demand: Long-tail keywords exist? Clear monetization path?
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-fortunto2-solo-validate": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
solo-swarm
Launch 3 parallel research agents (market, users, tech) to investigate an idea from multiple angles simultaneously. Use when user says "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or wants faster alternative to /research. Produces research.md. Do NOT use for solo research (use /research) or idea scoring (use /validate).
solo-build
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says "build it", "start building", "execute plan", "implement tasks", "ship it", or references a track ID. Do NOT use for planning (use /plan) or scaffolding (use /scaffold).
solo-metrics-track
Set up PostHog metrics plan with event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds. Use when user says "set up metrics", "track KPIs", "PostHog events", "funnel analysis", "when to kill or scale", or "success metrics". Do NOT use for SEO metrics (use /seo-audit).
solo-audit
Health check knowledge base for broken links, missing frontmatter, tag inconsistencies, and coverage gaps. Use when user says "audit KB", "check frontmatter", "find broken links", "tag cleanup", or "knowledge base quality". Do NOT use for SEO audits (use /seo-audit) or code reviews.
solo-seo-audit
SEO health check for any URL — analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, SERP positions, and scores 0-100. Use when user says "check SEO", "audit this page", "SEO score", "check meta tags", or "SERP position". Do NOT use for generating landing content (use /landing-gen) or social media posts (use /content-gen).