GitHub - zszendro/vc-teardown: A Claude Skill that stress-tests your startup idea as a skeptical VC, then rebuilds it into a business plan with a defensible moat, MVP scope, GTM and kill criteria. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
zszendro
vc-teardown
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>1 Commit<br>1 Commit
vc-teardown
vc-teardown
.gitignore
.gitignore
LICENSE
LICENSE
README.md
README.md
View all files
Repository files navigation
vc-teardown
A Claude Skill that stress-tests your startup idea as a skeptical VC — then rebuilds it into a plan with a defensible moat.
Describe a business idea in one line or ten pages. The skill researches who already built it, attacks it with the objections a real investor would raise, finds the wedge the incumbent structurally won't take, and writes the business plan, MVP scope, go-to-market and kill criteria.
Most ideas fail not because they're bad, but because the obvious version is already built. This skill is designed to find that out in an afternoon instead of six months.
What it does
1. Intake — takes whatever detail you have. No questionnaire; at most three questions, and only ones that change the analysis.
2. Research — searches for direct incumbents, free substitutes, adjacent software your buyer already pays for, and evidence the pain is real. This step is non-negotiable: skipping it produces generic startup advice.
3. Teardown — 8–12 numbered challenges drawn from a library of 16 attack surfaces. Every challenge ends in a concrete revision. Criticism that doesn't change the plan doesn't count.
4. Moat — the reframe. Nine patterns for finding defensibility, including the two that do most of the work: generate the data instead of aggregating it, and find the incumbent's metric mismatch.
5. Plan — market reality, tiered use cases, revenue lines ordered by when they turn on, unit economics with the actual arithmetic, MVP scope and stack, GTM, risk register, and falsifiable kill criteria.
6. Delivery — a written plan, plus an appendix mapping every element of your original idea to where it landed.
How it differs from other VC skills
There are several Claude skills in this space. Most of them score something you've already built — a pitch deck, a fundraising narrative, a named company you're evaluating. Some simulate specific investors' philosophies to grade your existing story.
This one starts earlier and ends differently. It takes a raw idea, establishes what's already been built in that market, kills the version that loses, and rebuilds the idea around a different moat . The teardown isn't the deliverable — the reframe is.
If you have a deck and want it graded, use one of the others. If you have an idea and want to know whether the obvious version of it is already dead, use this.
Why it's not a yes-man
Three constraints do the work:
It runs the numbers. If one fully-penetrated beachhead produces $18k of revenue, it writes that number. Especially then.
It states the honest scale verdict. Lifestyle business, bootstrap SaaS, or venture-scale — in plain words. Dressing an SMB SaaS as a venture marketplace fails diligence and wastes a year.
It names the cheapest test. The experiment that de-risks the biggest assumption usually costs time, not money — and it says explicitly what shouldn't be built until that test passes.
It's also calibrated not to be contrarian for sport. If a challenge has a good answer, it says so and moves on. Manufactured objections cost credibility on the real ones.
Install
Claude apps — download vc-teardown.skill from Releases and click Save skill on the file card in a conversation.
Claude Code — clone into your skills directory:
git clone https://github.com/zszendro/vc-teardown.git ~/.claude/skills/vc-teardown
Manual — copy the vc-teardown/ folder into wherever your setup loads skills from.
Use it
Just describe the idea. The skill triggers on its own:
I'm thinking about building a...