shipshitdev/idea-validator
bundles/startup/skills/idea-validator/SKILL.md
Validate startup ideas using Hexa's Opportunity Memo framework and Perceived Created Value (PCV) methodology. Assess problem-solution fit, market opportunity, and determine if an idea is worth pursuing.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library 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 8, 2026, 5:11 AM18.9s3 files scanned
SKILL.md
- name:
- idea-validator
- description:
- Validate startup ideas using Hexa's Opportunity Memo framework and Perceived Created Value (PCV) methodology. Assess problem-solution fit, market opportunity, and determine if an idea is worth pursuing.
- version:
- 1.0.0
- tags:
- business, hexa, validation, startup, idea, problem-solution-fit
Idea Validator - Startup Idea Assessment Framework
Rigorously assess startup ideas BEFORE building using structured validation—saving months of wasted effort on ideas that won't work.
Hexa's Principle: "You want to make something people want. But people don't always know what they want—so you need to understand what they actually need."
When This Activates
- User asks "is this a good idea"
- User says "I want to build X" without validation
- User asks "should I pursue this"
- User mentions a startup idea they're considering
- User wants to know if their idea is worth building
The Framework
Validation = Opportunity Memo Assessment + Perceived Created Value (PCV) Score
Problem Assessment Matrix
| Dimension | Rating | Impact | |-----------|--------|--------| | Frequency | [Daily/Weekly/Monthly] | High/Med/Low | | Severity | [Critical/Important/Nice-to-have] | High/Med/Low | | Awareness | [Actively seeking/Aware/Unaware] | High/Med/Low | | Budget | [Has budget/Would find/No budget] | High/Med/Low |
Problem Score: 3-4 High = Strong. 1-2 = Weak. 0 = Not a real problem.
PCV Scoring (4 Dimensions)
Rate current solution problems + your improvement:
| Dimension | Current Problem | Your Improvement | |-----------|-----------------|------------------| | Price | Not a problem / A problem / Serious | No diff / Some / Serious | | Quality | Not a problem / A problem / Serious | No diff / Some / Serious | | Performance | Not a problem / A problem / Serious | No diff / Some / Serious | | Convenience | Not a problem / A problem / Serious | No diff / Some / Serious |
Scoring: a=0, b=1, c=3 points. Sum all 8 ratings.
| Score | Interpretation | Recommendation | |-------|---------------|----------------| | 0-6 | Weak | Don't pursue | | 7-12 | Moderate | Needs refinement | | 13-18 | Strong | Worth pursuing | | 19-24 | Exceptional | Build NOW |
Quick Discovery Questions
Problem Space:
- What specific pain point does your ICP feel?
- How do they currently solve this?
- What's wrong with current solutions?
- How often do they experience this pain?
- What does this problem cost them?
Timing:
- Why is NOW the right time?
- What has changed recently?
- What barriers existed before that are now gone?
ICP:
- Company type, size, industry
- Buyer vs. user role
- What triggers them to seek a solution?
Integration
| Skill | When to Use |
|-------|-------------|
| market-sizer | After validation passes |
| startup-icp-definer | Deep dive on customer |
| mvp-architect | Scope the build |
| leads-researcher | Find design partners |
For detailed execution workflow, output templates, and PCV calculations: references/full-guide.md
Related Skills
shipshitdev/typescript-refactor
development
VerifiedTrustedCommunity
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/typescript-expert
tools
VerifiedTrustedCommunity
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/turborepo
tools
VerifiedTrustedCommunity
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/tailwind
tools
VerifiedTrustedCommunity
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
30SKILL.mdUpdated Jul 14, 2026