Pitch deck
Build a pitch deck for a crypto project. Use when the user says "pitch deck", "demo day", "investor presentation", "grant application slides", "accelerator application", "help me pitch", or needs slides for a hackathon final.From its SKILL.md
npx -y skills add solanabr/solana-ai-kit --skill pitch-deckAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
4.1 KB, 994 tokens by cl100k_base, as published. Nobody here has run it
Pitch Deck
Interview → detect audience → pick narrative → build slides with speaking notes → self-score → objection prep.
Context handoff
At start, read .claude/context/idea.md and .claude/context/build.md if present — pre-fill problem, wedge, traction, and stack from them; only ask what's missing.
Workflow
1. 12-question interview
Blunt, one at a time, skipping anything already answered by context files:
- What does it do, in one sentence a non-crypto person understands?
- Who exactly has the problem, and how painful is it (evidence)?
- Why does this need a blockchain?
- Why Solana specifically?
- What works today (demo-able) vs. roadmap?
- Traction numbers — users, volume, TVL, signups, waitlist?
- Who is the team and what's the unfair edge?
- Competitors and your moat?
- Business model — who pays, when?
- Who is the audience for this deck (judges, VCs, grant committee, accelerator)?
- The ask — prize, check size, grant amount, admission?
- Biggest weakness you're afraid they'll ask about?
2. Audience detection → slide set
Q10 decides the slide set — full breakdown in investor-audience-guide.md:
| Audience | Emphasis | Length |
|---|---|---|
| Hackathon judges | working demo, technical novelty, why-Solana | 5–7 slides |
| VC | market size, traction slope, team, moat, ask | 10–12 |
| Grant committee | ecosystem benefit, public-good angle, milestones, budget | 8–10 |
| Accelerator | team velocity, learning rate, wedge → expansion path | 8–10 |
Slide-by-slide order per audience: pitch-structure.md.
3. Narrative framework
Pick ONE backbone and state why — PAS (obvious pain, hackathons), 6-Part Investor Arc (VC), BAB (before/after/bridge), Hero's Journey (founder-story-driven), Pixar (narrative momentum). Definitions, slide mappings, and crypto examples: storytelling-frameworks.md.
4. Build slides + speaking notes
For each slide: headline (a claim, not a label), 3–5 supporting points, visual suggestion, and 30–60s speaking notes. Use:
- slide-templates.md — per-slide-type templates
- deck-design-system.md — typography, layout, color rules
- crypto-pitch-examples.md — real decks that worked
- pitch-reference-sources.md — primary sources
5. Self-score vs audience rubric
Score the draft against the audience's actual criteria (clarity, credibility, demo strength, ask specificity) and against crypto-pitch-mistakes.md — flag every mistake the deck still commits, fix, re-score. Don't present a deck you'd score below 8/10.
6. Objection-prep Q&A
From Q12 + the weakest scored dimension, draft the 8–10 hardest questions this audience will ask, each with a tight 30-second answer. Hostile-question drilling beats slide polish.
Output
- Deck outline (markdown, one section per slide: headline / points / visual / speaking notes)
- Framework choice + one-line rationale
- Self-score with the fixes applied
- Objection Q&A sheet
Need an actual rendered deck file (.pptx)? Hand the outline to the pptx skill if available.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most slides presentations skills give in 994 tokens
Counted across 547 of the 547 authors here whose files we hold, read 2026-09-06
- Ensure every slide fits inside one viewportin 31 of 547, across 18 files
- Keep one idea per slidein 27 of 547, across 24 files
- Default to one self-contained HTML filein 24 of 547, across 16 files
- Check for product marketing context firstin 21 of 547, across 7 files
- Read STYLE_PRESETS.md before generatingin 21 of 547, across 12 files
- Involve reps in creationin 20 of 547, across 6 files
- Tailor to persona and deal stagein 20 of 547, across 6 files
- Generate three single-slide preview filesin 17 of 547, across 11 files
- Delete temporary preview files at handoffin 16 of 547, across 8 files
- Support keyboard and touch navigationin 16 of 547, across 7 files
- Keep one-pagers to a single pagein 15 of 547, across 5 files
- Use bold headers and short bulletsin 14 of 547, across 4 files
Said here and by no other author read
- Conduct a 12-question interview
- Detect the audience to choose slides
- Pick a storytelling narrative backbone
- Self-score the draft against criteria
- Draft the hardest audience questions
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.