presentation-pitch-deck — Claude Code skill: investor decks that read
This skill drafts an investor pitch deck on the Sequoia or YC framework. Built for decks sent by email, where nobody presents alongside them.
npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a claude-codeWhat presentation-pitch-deck does
The skill walks the agent through a 10-slide structure: problem, solution, traction, market, business model, competition, team, financials, the ask. Traction can move up when the numbers are strong. Every slide gets a headline that survives without a speaker.
A separate section covers async reading. Headlines should be complete, data belongs in charts rather than paragraphs, and metrics should sit in text so a parser can pull them out. There is a forwardable test: if an associate passes the deck to a partner with no context, it still has to make sense. VC firms run decks through AI screening, so the skill asks you to format for extraction.
A mistake table lists the usual failures — no clear ask, features instead of benefits, a TAM pulled from thin air, 20+ slides. Format rules are concrete too: 10 slides, 15 max, PDF under 10MB named Company - Stage Deck - Month Year.pdf, high contrast so it stays readable at 50% zoom. Install runs through npx skills add; GitHub Copilot uses gh skill install.
What it helps with
- draft a 10-slide investor deck on the Sequoia or YC framework
- rewrite slides so they read without a presenter
- move metrics and charts onto the traction slide
- check a deck against common mistakes before sending it
- prepare a PDF that survives AI screening
Example prompts for the agent
- build a seed pitch deck using the YC framework
- check my deck against the mistakes table and tell me what to cut
- rewrite the slides for async reading so the deck works without me
How to install presentation-pitch-deck
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a claude-code2Manually: put the files in place
~/.claude/skills/presentation-pitch-deck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/presentation-pitch-deck/
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a codex2Manually: put the files in place
.agents/skills/presentation-pitch-deck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a cursor2Manually: put the files in place
.cursor/skills/presentation-pitch-deck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aaronvanston/skills-presentations presentation-pitch-deck2Manually: put the files in place
.github/skills/presentation-pitch-deck/SKILL.md1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a gemini-cli2Platform CLI
gemini skills install https://github.com/aaronvanston/skills-presentations --path skills/presentation-pitch-deckManually: put the files in place
.devin/skills/presentation-pitch-deck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-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 presentation-pitch-deck
How do I install presentation-pitch-deck in Claude?
Run npx skills add aaronvanston/skills-presentations --skill presentation-pitch-deck -a claude-code. The skill lands at ~/.claude/skills/presentation-pitch-deck/SKILL.md.
What does presentation-pitch-deck do?
It guides the agent through a 10-slide investor deck structure and insists every slide stand alone without a presenter. It also covers PDF format and common mistakes.
How is a pitch deck different from a presented deck?
A presented deck carries little text because the speaker supplies context. A pitch deck holds more text, shows traction in charts, and gives the ask its own slide — investors study it for 30–60 seconds instead of glancing for three.
Source text
SKILL.md · MIT
---
name: presentation-pitch-deck
description: Create investor pitch decks designed to stand alone without a presenter. Follows Sequoia/YC frameworks with traction-first structure and standalone readability. Use when creating a "pitch deck", "investor presentation", "fundraising deck", or any deck sent async to investors, partners, or stakeholders who won't have the presenter alongside.
---
# Pitch Deck
Create investor-ready pitch decks that get meetings, pass AI screening, and tell your story without you in the room.
## Pitch Deck vs. Presented Deck
| Aspect | Presented Deck | Pitch Deck |
|--------|---------------|------------|
| Text density | Minimal — speaker adds context | Higher — must stand alone |
| Structure | Flexible narrative | Expected frameworks (Sequoia, YC) |
| Traction | Discussed verbally | Shown prominently with charts |
| The Ask | Built to naturally | Explicit dedicated slide |
| Length | Flexible | 10-15 slides max |
| Reading speed | 3 sec/slide (glance media) | 30-60 sec/slide (studied) |
## The 10-Slide Framework
### Slide 1: Title
Company name, one-line description, contact info, optional traction hook.
### Slide 2: Problem
The pain point — who experiences it, why it's urgent. Lead with customer quotes or data. If the problem isn't real or urgent, nothing else matters.
### Slide 3: Solution
Product in 30 seconds. Show transformation ("Before → After"), not feature lists.
### Slide 4: Traction
Charts over text. Revenue, users, growth rate, milestones, customer logos. Move this earlier if numbers are strong.
### Slide 5: Market Size
TAM, SAM, SOM with clear definitions. Bottom-up calculation preferred. Why now?
```markdown
**TAM:** $X global market
**SAM:** $Y — target segment in target geographies
**SOM:** $Z — specific niche you're capturing now
```
### Slide 6: Business Model
How you make money. Pricing structure, unit economics (CAC, LTV, payback), path to profitability.
### Slide 7: Competition
Competitive landscape (matrix or quadrant). Your differentiation. Never say "no competition."
### Slide 8: Team
Photos, names, one-line credentials. Why this team wins. Key advisors if notable.
### Slide 9: Financials & Roadmap
Revenue projections (realistic), key milestones, use of funds preview, path to next round.
### Slide 10: The Ask
Amount, use of funds breakdown, milestones it unlocks, clear CTA.
```markdown
**Raising:** $XM [Stage]
**Use of Funds:**
- 50% Product (core features, AI capabilities)
- 30% Go-to-market (sales team, partnerships)
- 20% Operations (support, infrastructure)
**Next step:** 30-minute call to discuss partnership
```
## Writing for Async Reading
### Headlines: Bold but complete
```
Bad: "Traction" (too sparse for async)
Good: "1,000+ Customers, $10M ARR, 10% MoM Growth"
```
### Body text: More context, still scannable
- 2-3 bullet points per section, each a complete thought
- Bold the key phrase, explain after
### Data: Always visualize
Charts > Tables > Bullets > Paragraphs
### The "Forwardable" Test
If an associate forwards this to a partner with no context, does it make sense?
## AI Screening
Modern VC firms use AI to screen decks. Optimize for extraction:
- Clear slide titles matching expected categories
- Metrics in text, not just images
- Consistent formatting so data can be parsed
## Common Mistakes
| Mistake | Why it fails |
|---------|-------------|
| No clear ask | Investors don't know what you want |
| Features over benefits | They care about outcomes, not specs |
| TAM fantasy | "$1T market" without credible math |
| No traction proof | Words without evidence |
| Too many slides | 20+ signals lack of focus |
| No team photos | Feels impersonal, forgettable |
## Format Guidelines
- **10 slides ideal**, 15 max. Appendix slides clearly separated.
- **PDF for sending** — under 10MB, named `Company - Stage Deck - Month Year.pdf`
- **High contrast** for data visualization, readable at 50% zoom (how VCs often review)
## Workflow
1. **Clarify the raise** — stage, amount, use of funds
2. **Identify traction** — what's the strongest proof point?
3. **Choose framework** — Sequoia (story-driven) or YC (traction-driven)
4. **Draft 10 slides** — one idea per slide
5. **Apply forwardable test** — does each slide work standalone?
6. **Cut ruthlessly** — every slide must earn its place
© aaronvanston · MIT · aaronvanston/skills-presentations