idea-validator
Skill0 starsChanged 22 days agoMITView on GitHub
Stress-test a new business, product or SaaS idea: users, pain, competitors, cost, distribution, riskiest assumption, cheapest validation experiment. Use for "validate this idea", "new product idea", "would this work". NOT agency decisions (founder-strategy).
13 other projects use a version of this.
Adopted by
Most recently taken up by
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- luongnv89/skillstheir own version, first seen Nov 6, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- PyDaft/idea-validator-skilltheir own version, first seen Nov 1, 2026
- hongphuc5497/skillstheir own version, first seen Nov 1, 2026
- jaredhhawk/claude-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use prd-generator and prompt-engineer.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dhzrxSkillprd-generator
Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products
Also in 3 projects that use this
JeffallanSkillprompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON/function-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Mathews-Tom/armory★ 340same name
- luongnv89/skills★ 145same name
- aakashg/pm-claude-skills★ 106same name
- HK-hub/AgentSkills★ 6same name
- patonkikh/APES★ 3same name
- dipaulavs/ClaudeCode-Workspace-2025★ 2same name
- hongphuc5497/skills★ 2same name
- samsam007b/claude-code-standards-kit★ 2same name
- dersi3/idea-validator-skill★ 0same name
- jaredhhawk/claude-skills★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- backend-architectureSkill
- build-review-loopSkill
- capability-intakeSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- dev-patternsSkill
- frontend-system-designSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
- update-mdSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
Distinctive
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 29
Write directly and specifically.
- Distinctive: line 30
Never reveal client secrets or personally identifying data unnecessarily.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
idea-validator
Purpose
Stress-test new business and software ideas. Use concrete evidence and project-specific constraints. Do not claim work was executed, tested, legally approved, or verified unless it actually was.
Activation
Activate when the request concerns stress-test new business and software ideas. Read relevant project instructions first. When current laws, platform APIs, or tool capabilities matter, check authoritative current sources.
Procedure
- Define users and pain points.
- Map competitors and substitutes.
- Estimate cost and distribution.
- List highest-risk untested assumption.
- Design inexpensive validation experiment.
Verification gate
- State what was examined, what was not accessible, and any assumptions.
- Separate confirmed findings, risks, recommendations, and unverified hypotheses.
- For development, require relevant automated tests and manual checks before marking complete.
- Provide exact file paths/line references, data sources, or legal citations when appropriate.
- Report blockers and proposed fixes by severity. Never silently change production systems.
the agency editorial and safety rules
- Write directly and specifically. No generic AI fluff, em dashes, exaggerated claims, artificial case studies, unnecessary dividers, or fabricated proof.
- Never reveal client secrets or personally identifying data unnecessarily. Use redacted examples and placeholders.
- Seek explicit approval before sending external communication, changing production, deploying code, deleting data, or conducting active security tests.
- For regulated legal or tax conclusions, provide research support, not a claim of professional sign-off.
Deliverable template
- Scope and context, 2. Evidence and findings, 3. Prioritized action plan, 4. Validation/acceptance criteria, 5. Uncertainties or approvals needed. Adapt format to the actual request rather than forcing five headings.
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.

