$npx -y skills add ferdinandobons/startup-skill --skill startup-pitchBuild investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investo
| 1 | # Startup Pitch |
| 2 | |
| 3 | Build investor-ready pitch content in multiple formats. Uses a structured 7-element framework combined with a problem-solution-insight foundation to produce pitch narratives that are clear, compelling, and fundable. |
| 4 | |
| 5 | ## How It Works |
| 6 | |
| 7 | ``` |
| 8 | INTAKE → RESEARCH (2 sequential waves) → PITCH CONSTRUCTION → REVIEW & PRACTICE |
| 9 | ``` |
| 10 | |
| 11 | The process: understand the company deeply, research the investor audience and competitive framing, then construct the pitch. Typical runtime: 15-20 minutes in Claude Code (parallel agents), 30-40 minutes in Claude.ai (sequential). |
| 12 | |
| 13 | ### Core Philosophy |
| 14 | |
| 15 | Three principles govern every output this skill produces: |
| 16 | |
| 17 | 1. **Clarity over sophistication.** "80% accurate and 100% clear beats the reverse." If a grandmother can't understand what you do, investors won't either. Eliminate jargon, acronyms, and marketing language. |
| 18 | 2. **Lead with what's impressive.** You earn each additional minute of investor attention. Don't bury traction after 5 sections of problem setup — put the strongest signal right after "what you do." |
| 19 | 3. **Make investors talk.** A pitch isn't a monologue. The more investors talk, the more they convince themselves. Structure the narrative to invite conversation, not shut it down. |
| 20 | |
| 21 | ### Language |
| 22 | |
| 23 | Default output language is **English**. If the user writes in another language or explicitly requests one, use that language for all outputs instead. |
| 24 | |
| 25 | --- |
| 26 | |
| 27 | ## Phase 0: Resume Check |
| 28 | |
| 29 | Before anything else, check if a `PROGRESS.md` created by this skill exists in the working directory or a project subdirectory (the skill name field says `startup-pitch`). If it does, read it and resume from the last incomplete phase. Tell the user: "I found progress from a previous session. You completed [phases]. Picking up from [next phase]." |
| 30 | |
| 31 | If no progress file exists — or the one found belongs to a different skill — start from Phase 1. |
| 32 | |
| 33 | --- |
| 34 | |
| 35 | ## Phase 1: Intake |
| 36 | |
| 37 | Short and focused — 1-2 rounds of questions. The goal is enough context to build a compelling pitch. |
| 38 | |
| 39 | ### Recommended Prior Work |
| 40 | |
| 41 | A pitch built on validated data is significantly stronger than one built on self-reported answers. If you haven't already, consider running **startup-design** first — it provides market research, competitive analysis, business model, financial projections, and a validation scorecard that become the foundation of a much more credible pitch. |
| 42 | |
| 43 | Not required. startup-pitch works standalone. But the quality difference is noticeable. |
| 44 | |
| 45 | ### Check for Prior Work |
| 46 | |
| 47 | Before asking questions, check if prior sessions have been completed. Look for these files in the working directory or subdirectories: |
| 48 | |
| 49 | **From startup-design:** |
| 50 | - `00-intake/brief.md` — product description and context |
| 51 | - `01-discovery/market-analysis.md` — market size, TAM/SAM/SOM |
| 52 | - `01-discovery/competitor-landscape.md` — competitor profiles |
| 53 | - `01-discovery/target-audience.md` — customer personas, pain points |
| 54 | - `02-strategy/lean-canvas.md` — business model summary |
| 55 | - `02-strategy/positioning.md` — positioning framework |
| 56 | - `05-financial/revenue-model.md` — revenue projections |
| 57 | - `06-validation/scorecard.md` — idea scorecard |
| 58 | |
| 59 | **From startup-competitors:** |
| 60 | - `competitors-report.md` — competitive landscape |
| 61 | - `battle-cards/` — per-competitor profiles |
| 62 | - `pricing-landscape.md` — pricing analysis |
| 63 | |
| 64 | **From startup-positioning:** |
| 65 | - `positioning-doc.md` — positioning document |
| 66 | - `positioning-statement.md` — positioning statements, elevator pitch |
| 67 | - `competitive-alternatives.md` — alternatives map |
| 68 | - `messaging-implications.md` — messaging hierarchy |
| 69 | |
| 70 | If these files exist, read them and extract the pitch building blocks: product description, problem/solution, traction, team, market size, business model, positioning, competitive landscape. Tell the user: "I found data from a previous session. I'll use it to build your pitch." |
| 71 | |
| 72 | Skip redundant intake questions. Go straight to pitch-specific questions if prior data is sufficient. |
| 73 | |
| 74 | ### What to Ask (if no prior data exists) |
| 75 | |
| 76 | **Round 1 — The essentials (all required for a pitch):** |
| 77 | - What does your company do? (2 sentences max — this becomes the opening) |
| 78 | - What problem are you solving and for |