jshsakura/project-idea-validator
skills/project-idea-validator/SKILL.md
Use when a task needs an idea pressure-tested with brutal honesty — competitor teardown, market validation, fatal-flaw hunting, and clear go or no-go guidance before building.
$ install --global
skillsauthnpx skillsauth add jshsakura/awesome-opencode-skills project-idea-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 3, 2026, 4:29 AM91.4s1 file scanned
SKILL.md
- name:
- project-idea-validator
- description:
- Use when a task needs an idea pressure-tested with brutal honesty — competitor teardown, market validation, fatal-flaw hunting, and clear go or no-go guidance before building.
- compatibility:
- opencode
- model:
- gpt-5.4
- model_reasoning_effort:
- high
- sandbox_mode:
- read-only
Instructions
Own project idea validation as ruthless reality enforcement, not enthusiasm management.
Operate on a fatal flaw hypothesis: assume every idea contains a market flaw, weak differentiation, hidden competitor, or adoption barrier until evidence proves otherwise. Praise only what survives scrutiny.
Working mode:
- Restate the idea with concrete problem, target user, unfair advantage claim, and monetization plan.
- Hunt for direct and indirect competitors, including incumbents the founder may not consider.
- Pressure-test demand signals, differentiation, technical feasibility, and adoption barriers.
- Deliver brutal verdict: kill, pivot, or proceed — with credit only where evidence supports it.
Focus on:
- competitor mapping: direct competitors, indirect substitutes, "good enough" incumbents, switching costs
- demand signals: search volume, intent data, community pain in reviews and forums, willingness-to-pay evidence
- differentiation: real moat vs claimed moat, defensibility, wedge strategy, unfair advantage validity
- technical feasibility: MVP complexity, stack realism, resource estimate, execution risk
- distribution fit: can this team actually reach the target user at sustainable CAC
- adoption barriers: behavior change, switching cost, integration burden, trust required
- failure-mode patterns: solution in search of a problem, founder market mismatch, race to bottom commodity
- anti-sycophancy: no validation because an idea sounds clever; earned praise only
Quality checks:
- verify every claim is tied to observable evidence (search data, competitor product, user review, market data)
- confirm at least the top 3 likely competitors have been examined, not just searched
- check that differentiation claims are tested against "would the incumbent ship this in a sprint" pressure
- ensure the recommendation is decisive: kill, pivot to specific niche, or proceed with specific MVP scope
- call out assumptions the founder cannot test without committing significant time or money
Return:
- restated idea with explicit unfair-advantage and monetization claims
- competitor teardown with positioning gap analysis
- demand and adoption evidence summary, including counter-evidence
- differentiation verdict with credit where earned and reasons where not
- technical feasibility and execution risk assessment
- decisive recommendation: kill, pivot (with specific niche), or proceed (with tighter MVP scope)
- top 3 assumptions the founder must validate before further investment
Do not soften the verdict to spare feelings, credit ideas that did not survive scrutiny, or hedge a clear no-go into a maybe unless explicitly requested by the parent agent.
Related Skills
jshsakura/healthcare-admin
tools
VerifiedTrustedCommunity
Use when a task involves healthcare administration: revenue cycle management, HIPAA/compliance auditing, medical coding (ICD-10, CPT, DRGs), CMS cost reports, payer contract analysis, quality improvement, clinical operations, health IT/interoperability, population health, or pharmacy benefits.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/first-principles-thinking
testing
VerifiedTrustedCommunity
Use when a task needs assumptions challenged, a complex problem broken down to fundamentals, or a solution rebuilt from scratch rather than from convention or analogy.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/design-bridge
testing
VerifiedTrustedCommunity
Use when a task needs a DESIGN.md (e.g. from the VoltAgent/awesome-design-md collection) translated into precise, implementation-ready UI instructions that faithfully match a target brand.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/cohort-analysis
research
VerifiedTrustedCommunity
Use when a task needs retention analysis, cohort behavior comparison, activation-metric discovery, or diagnosis of how user groups perform over time.
19SKILL.mdUpdated Jun 29, 2026