mohitagw15856/startup-idea-validator
skills/startup-idea-validator/SKILL.md
Pressure-test a startup idea the way a sharp investor or co-founder would — problem, market, wedge, moat, why-now, and the fastest cheap way to test it. Use when asked to validate a startup idea, evaluate a business idea, stress-test a concept, or decide whether something is worth building. Produces an honest assessment with the strongest case, the killer risks, and the next experiment to run — not cheerleading.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills startup-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 22, 2026, 7:02 AM76.0s1 file scanned
SKILL.md
- name:
- startup-idea-validator
- description:
- Pressure-test a startup idea the way a sharp investor or co-founder would — problem, market, wedge, moat, why-now, and the fastest cheap way to test it. Use when asked to validate a startup idea, evaluate a business idea, stress-test a concept, or decide whether something is worth building. Produces an honest assessment with the strongest case, the killer risks, and the next experiment to run — not cheerleading.
Startup Idea Validator Skill
Most ideas die from one fatal flaw the founder won't see. This skill plays the constructive skeptic: it makes the strongest case for the idea, then attacks it hard, and ends with the cheapest test that would move the founder's confidence the most.
Working from a brief
Given a one-line idea, deliver the full assessment anyway — infer the market and model, and mark assumptions. Be honest, not harsh or sycophantic: the goal is a better decision, not a verdict that feels good.
Required Inputs
Ask for (if not already provided):
- The idea — what it is and who it's for
- The problem it solves and how people cope today
- Why the founder is drawn to it (context for founder-market fit)
- Stage — just an idea, a prototype, early users?
Output Format
1. Steel-man — the strongest case for
The most compelling version of why this could be big. Take it seriously.
2. Scorecard
| Dimension | Read | Notes | |---|---|---| | Problem (real & painful?) | 🟢/🟡/🔴 | | | Market (big & reachable?) | 🟢/🟡/🔴 | | | Wedge (sharp entry point?) | 🟢/🟡/🔴 | | | Why-now (what changed?) | 🟢/🟡/🔴 | | | Moat (defensible over time?) | 🟢/🟡/🔴 | | | Distribution (can you reach buyers cheaply?) | 🟢/🟡/🔴 | |
3. The killer risks
The 2–3 things most likely to kill this. Be specific — name the assumption that, if false, ends it.
4. Closest competitors / why-not-already
Who's near this, and the honest answer to "if this is a good idea, why doesn't it exist / why hasn't [incumbent] done it?"
5. The next experiment
The single cheapest, fastest test that would most change your confidence — what to do this week, and what result would be a green vs red light.
6. Verdict
Promising / Promising-with-conditions / Reconsider — with the one sentence that decides it.
Quality Checks
- [ ] Steel-mans the idea before critiquing it
- [ ] Names specific killer assumptions, not generic "execution risk"
- [ ] Answers "why doesn't this already exist?"
- [ ] Ends with a concrete, cheap, this-week experiment
Anti-Patterns
- Cheerleading (validating because the founder wants a yes)
- Generic critique that applies to any startup
- Recommending a 6-month build as the "test"
- A verdict with no path forward
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026