startup-pitch
Build 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 investor meetings, craft a startup pitch, write a fundraising narrative, or practice their pitch. Triggers for "pitch deck", "investor pitch", "pitch my startup", "fundraising deck", "seed deck", "how to pitch", "investor meeting", "demo day", "prepare pitch", "pitch script", "elevator pitch for investors", "pitch practice", "practice my pitch", "investor roleplay", or any request to present a startup to investors, accelerators, or partners. Works standalone — no prior startup-design session needed, but leverages its output if available.
What this skill does
# Startup Pitch
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.
## How It Works
```
INTAKE → RESEARCH (2 parallel waves) → PITCH CONSTRUCTION → REVIEW & PRACTICE
```
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).
### Core Philosophy
Three principles govern every output this skill produces:
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.
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."
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.
### Language
Default output language is **English**. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
---
## Phase 1: Intake
Short and focused — 1-2 rounds of questions. The goal is enough context to build a compelling pitch.
### Recommended Prior Work
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.
Not required. startup-pitch works standalone. But the quality difference is noticeable.
### Check for Prior Work
Before asking questions, check if prior sessions have been completed. Look for these files in the working directory or subdirectories:
**From startup-design:**
- `00-intake/brief.md` — product description and context
- `01-discovery/market-analysis.md` — market size, TAM/SAM/SOM
- `01-discovery/competitor-landscape.md` — competitor profiles
- `01-discovery/target-audience.md` — customer personas, pain points
- `02-strategy/lean-canvas.md` — business model summary
- `02-strategy/positioning.md` — positioning framework
- `05-financial/revenue-model.md` — revenue projections
- `06-validation/scorecard.md` — idea scorecard
**From startup-competitors:**
- `competitors-report.md` — competitive landscape
- `battle-cards/` — per-competitor profiles
- `pricing-landscape.md` — pricing analysis
**From startup-positioning:**
- `positioning-doc.md` — positioning document
- `positioning-statement.md` — positioning statements, elevator pitch
- `competitive-alternatives.md` — alternatives map
- `messaging-implications.md` — messaging hierarchy
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."
Skip redundant intake questions. Go straight to pitch-specific questions if prior data is sufficient.
### What to Ask (if no prior data exists)
**Round 1 — The essentials (all required for a pitch):**
- What does your company do? (2 sentences max — this becomes the opening)
- What problem are you solving and for whom?
- What's your unique insight? (What do you know that others don't?)
- What traction do you have? (users, revenue, growth rate — with timeframes). If none: say so honestly, we'll build the pitch around insight and team instead.
- What's your business model? (one sentence — how do you make money?)
- Who's on the team? (names, roles, key accomplishments — not titles)
- How much are you raising and what will you do with it?
**Round 2 — Sharpening (only if needed):**
- What's your market size? (or enough data to calculate it)
- Who are your main competitors? What's your advantage?
- What milestones will you hit in 18-24 months with this funding?
**Pitch-specific questions:**
- Who is the audience? (VCs, angels, accelerator, demo day, specific fund?)
- What formats do you need? (10-min narrative, 2-min verbal, email pitch, all of them?)
Don't over-interview. A founder with clear answers to Round 1 has enough to build a strong pitch.
### The 2-Sentence Test
Before moving to research, crystallize the company description into exactly 2 sentences + one specific example. This is the foundation of the entire pitch.
Test: send it to a smart friend — could they paraphrase it back correctly? If not, simplify further.
> **Anti-pattern:** "We leverage AI-powered machine learning to optimize cross-functional synergies in the B2B SaaS vertical."
> **Better:** "We help sales teams find which leads will actually buy. Our tool analyzes email replies and tells reps exactly who to call next — last month one customer closed 40% more deals."
### Output
Save to `{project-name}/intake.md` — consolidated context for pitch construction. Project name: kebab-case (e.g., `ai-sales-assistant`).
Create `{project-name}/PROGRESS.md` with: project name, skill name (`startup-pitch`), start date, language, requested formats, target audience, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes.
---
## Phase 1.5: Research Depth Assessment
After intake, assess market complexity and present the Research Depth recommendation to the user.
> **Reference:** Read `references/research-scaling.md` for the complexity scoring matrix, tier definitions, wave configurations, and the user communication template.
### Process
1. Score three factors from the intake: market breadth (1-3), known competitors (1-3), geographic scope (1-3)
2. Sum the scores (range 3-9) and map to a tier: Light (3-4), Standard (5-7), Deep (8-9)
3. Present the Research Depth table to the user (see `research-scaling.md` for the exact template)
4. Wait for user response: **light**, **deep**, or **ok** to accept the recommendation
5. Record the selected tier in PROGRESS.md
The selected tier determines the number of agents per wave and search rounds per agent in Phase 2. See `research-scaling.md` for exact wave configurations per tier.
---
## Phase 2: Research
Two parallel research waves exploring investor audience and competitive/market framing. Together they provide the raw material for a pitch that resonates with the target audience.
### Environment Detection
Check if the `Agent` tool is available:
- **Agent tool available (Claude Code):** Spawn all agents within each wave in parallel. This is faster.
- **Agent tool NOT available (Claude.ai, web):** Execute research sequentially, following the same templates. Same depth, just slower.
### Web Search
If WebSearch is unavailable, fall back to **Knowledge-Based Mode**: use training data, mark findings with **[Knowledge-Based — verify independently]**, and reduce confidence ratings by one level. Note the mode in PROGRESS.md.
> **Reference:** Read `references/research-principles.md` before starting any wave. It defines source quality tiers, cross-referencing rules, and how to handle data gaps.
### Wave 1: Audience & Narrative Intelligence
> **Reference:** Read `references/research-wave-1-audience-narrative.md` for agent templates.
Two agents (or two sequential blocks):
**A1: Investor & Audience Intelligence** — Research the target audience (VC firms, angels, accelerators). What are they investing in? What thesis do they follow? What metrics matter at this stage? What are red flags for them? What's the current fundraising climate in this space? Build an audience profile that shapes how the pitch is framed.
**A2: CRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.