vc-pitch-deck — Claude Code skill: what it does, how to install
vc-pitch-deck is a Claude Code skill that creates, reviews, and revises investor decks and slides. It prepares materials for email, presentations, and demo days.
MIT 102 installs ★ 655 updated 2026-10-20
npx skills add pedronauck/skills --skill vc-pitch-deck -a claude-codeWhat vc-pitch-deck does
The skill builds new pitch decks or edits specific slides based on supplied facts and narrative context. It relies on reference files that define slide sequences, anatomy rules, metric standards, and teardown rubrics for various fundraising formats. When handling financials, markets, and proof points, the agent validates data sources and separates assumptions from hard facts.
For devtools and AI infrastructure positioning, it utilizes canonical guides from the related vc-strategy skill if available. The agent leaves unsupported claims and unverified growth metrics out of slides, flagging missing evidence during the draft process.
What it helps with
- draft investor pitch deck slides
- review existing presentation against teardown rubric
- format financial and metric proof slides
- revise slide headlines for clarity
Example prompts for the agent
- Create a pitch deck for our seed round using the provided narrative
- Review this traction slide for missing metric sources
- Fix the structure of our market size slide
How to install vc-pitch-deck
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill vc-pitch-deck -a claude-code2Manually: put the files in place
~/.claude/skills/vc-pitch-deck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vc-pitch-deck/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill vc-pitch-deck -a codex2Manually: put the files in place
.agents/skills/vc-pitch-deck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill vc-pitch-deck -a cursor2Manually: put the files in place
.cursor/skills/vc-pitch-deck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pedronauck/skills skills/mine/vc-pitch-deck2Manually: put the files in place
.github/skills/vc-pitch-deck/SKILL.md1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill vc-pitch-deck -a gemini-cli2Platform CLI
gemini skills install https://github.com/pedronauck/skills --path skills/mine/vc-pitch-deckManually: put the files in place
.devin/skills/vc-pitch-deck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pedronauck/skills --skill vc-pitch-deck -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vc-pitch-deck
How to install vc-pitch-deck in Claude Code?
Run npx skills add pedronauck/skills --skill vc-pitch-deck -a claude-code followed by ~/.claude/skills/vc-pitch-deck/SKILL.md.
What does vc-pitch-deck do?
It generates, inspects, and revises investor presentations and individual slides, ensuring proper structure for demo days, meetings, and send-ahead formats.
Does the skill integrate with other tools?
Yes, it references positioning guides from the related vc-strategy skill when that tool is installed in your environment.
Source text
SKILL.md · MIT
--- name: vc-pitch-deck description: "Create, review, or revise investor decks and individual slides, including send-ahead, presented, and demo-day variants. vc-strategy owns fundraising strategy/narrative; vc-outreach owns investor outreach and meetings." --- # VC Pitch Deck Create or improve the requested deck artifact. For an existing deck or one slide, work from the supplied narrative and facts; do not restart a full fundraising strategy exercise. 1. Resolve the audience, format, and intended decision from context. Identify the evidence available and consequential missing facts. 2. For a new deck, use the relevant sequence in `references/sequences-and-variants.md`; choose the slides the story needs, not a fixed count or five separate variants. 3. Draft/edit the affected slides using their sections in `references/slide-anatomy.md`. Keep the opening concrete, headlines coherent, and each slide legible. Word counts and one-visual rules are format heuristics, not automatic failures. 4. For metrics, market, financials, or ask slides, use `references/proof-slides.md`: source numbers, label period/unit, distinguish facts from assumptions, and make the ask explicit. Verify current benchmarks before using them as market evidence. 5. Use the relevant part of `references/teardown-rubric.md`: a quick skim and headline read for the story, then inspect weak/changed slides. A full slide-by-slide teardown belongs to a full review request. Fix material issues without endless cosmetic passes. 6. Deliver the requested editable content and/or exported PDF, with unresolved evidence gaps. Add appendix material for real objections; no minimum appendix count or daily refinement quota. Publishing/sending requires separate authorization unless already provided. For devtools/AI-infra positioning, use the canonical `../vc-strategy/references/devtools-positioning.md` when installed; otherwise work from the supplied product evidence and verify missing facts. Do not invent a moat, growth channel, or pedigree claim to fill a slide.
© pedronauck · MIT · pedronauck/skills