pitch-deck
Generate professional PowerPoint pitch decks for startups and businesses. Use this skill when users request help creating investor pitch decks, sales presentations, or business pitch presentations. The skill follows standard 10-slide pitch deck structure and includes best practices for content and design.
What this skill does
# Pitch Deck Generator
## Overview
Generate professional PowerPoint pitch decks following industry best practices. This skill creates structured presentations for fundraising, sales, and business development using a proven 10-slide format.
## When to Use This Skill
Activate this skill when users request:
- Investor pitch decks for fundraising
- Sales or business development presentations
- Product launch presentations
- Startup pitch competition decks
- Any structured business presentation following standard pitch deck format
## Workflow
### Step 1: Gather Information
Collect necessary information from the user to populate the pitch deck. Use a conversational approach to gather details across the following categories:
**Required information:**
1. **Company basics**: Company name, tagline (one-liner describing what you do)
2. **Problem**: What problem are you solving? Include data or statistics if available
3. **Solution**: How does your product/service solve the problem? Key features and benefits
4. **Business model**: How do you make money? Pricing, revenue streams
**Recommended information** (include if available):
5. **Market opportunity**: Market size (TAM/SAM/SOM), growth rate, market trends
6. **Product details**: Product features, screenshots, technology highlights
7. **Traction**: Key metrics, revenue, users, growth rate, milestones, customer testimonials
8. **Competition**: Competitors, competitive advantages, differentiation
9. **Team**: Founders and key team members with relevant background
10. **Financials & Ask**: Funding amount, use of funds, financial projections, milestones
**Approach:**
- Ask open-ended questions to understand the business
- Probe for specific metrics and data points when possible
- For missing information, offer to create placeholder slides that can be updated later
- Adapt the standard 10-slide structure based on available information
### Step 2: Structure the Content
Organize the gathered information into the standard pitch deck structure:
1. **Title Slide**: Company name + tagline
2. **Problem**: Pain point being addressed
3. **Solution**: Product/service overview
4. **Market Opportunity**: Market size and growth
5. **Product**: Features and capabilities
6. **Traction**: Metrics and achievements
7. **Business Model**: Revenue and pricing
8. **Competition**: Competitive landscape
9. **Team**: Key people
10. **Financials & Ask**: Funding request and projections
**Reference best practices:** For detailed guidance on each slide's content and structure, consult `references/pitch_deck_best_practices.md`. Search for specific sections using grep:
```bash
grep -A 10 "### [Slide Number]. [Slide Name]" references/pitch_deck_best_practices.md
```
### Step 3: Create the JSON Data File
Format the collected information as a JSON file that will be consumed by the pitch deck generation script. Create a file called `pitch_data.json` with the following structure:
```json
{
"company_name": "Company Name",
"tagline": "One-line description of what you do",
"problem": [
"Problem statement 1 with data/statistics",
"Problem statement 2 showing impact",
"Problem statement 3 demonstrating urgency"
],
"solution": [
"How your product solves the problem",
"Key feature 1 and its benefit",
"Key feature 2 and its benefit",
"Unique value proposition"
],
"market": [
"TAM: Total addressable market with $ figure",
"SAM: Serviceable available market",
"SOM: Serviceable obtainable market",
"Market growth rate and trends"
],
"product": [
"Product feature 1",
"Product feature 2",
"Technology highlights",
"User experience benefits"
],
"traction": [
"Revenue: $X (YY% growth)",
"Users: X,XXX active users",
"Key milestone 1",
"Customer testimonial or social proof"
],
"business_model": [
"Revenue model (e.g., SaaS subscription)",
"Pricing: $XX/month per user",
"Unit economics: CAC, LTV, margins",
"Sales channels"
],
"competition": {
"our_advantages": [
"Advantage 1",
"Advantage 2",
"Unfair advantage/defensibility"
],
"competitors": [
"Competitor 1",
"Competitor 2",
"Alternative solutions"
]
},
"team": [
"Founder 1: Name - Background and relevant experience",
"Founder 2: Name - Background and relevant experience",
"Key hire: Name - Background and why they matter",
"Notable advisors"
],
"financials": [
"Raising: $X seed/Series A round",
"Use of funds: XX% engineering, XX% sales, XX% ops",
"Milestones with this funding",
"Runway: X-X months to next milestone"
]
}
```
**Notes:**
- All fields are optional except `company_name`
- Use arrays for bullet points (will be rendered as bullet lists)
- Competition can be either an object with `our_advantages` and `competitors` keys (for two-column layout) or a simple array
- Keep bullet points concise (1-2 lines each)
- Include specific numbers and metrics where possible
### Step 4: Generate the PowerPoint
Execute the Python script to create the PowerPoint presentation:
```bash
python3 scripts/create_pitch_deck.py pitch_data.json output_filename.pptx
```
The script will:
- Generate a professional PowerPoint file with proper formatting
- Apply consistent color scheme and typography
- Create slides based on available data (skipping sections if data not provided)
- Output a `.pptx` file ready for presentation or further customization
### Step 5: Review and Iterate
Present the generated pitch deck location to the user and offer to:
- Add missing sections if information becomes available
- Refine bullet points for clarity and impact
- Adjust structure based on specific audience (investor vs. sales pitch)
- Provide guidance on presenting the deck
**Iteration approach:**
- User can update the JSON file with new information
- Re-run the script to regenerate the updated presentation
- For design customizations beyond the script's capabilities, advise manual editing in PowerPoint
## Design Guidelines
The generated pitch deck follows these design principles:
**Color Scheme:**
- Primary: Blue (#2962FF) for titles and emphasis
- Secondary: Gray (#646464) for body text
- Clean white background for readability
**Typography:**
- Title slides: 54pt bold
- Section titles: 40pt bold
- Body text: 18-20pt with appropriate line spacing
**Layout:**
- Consistent margins and spacing
- One key message per slide
- Bullet points limited to 3-5 items per slide
- Two-column layouts for comparison slides
**Visual Hierarchy:**
- Clear title at top of each slide
- Content organized with proper spacing
- Emphasis on readability and professional appearance
## Best Practices Reference
For detailed guidance on pitch deck content, structure, and presentation tips, reference:
- `references/pitch_deck_best_practices.md` - Comprehensive guide covering:
- Standard 10-slide structure with examples
- Content guidelines for each slide type
- Design best practices
- Common mistakes to avoid
- Tailoring for different audiences (investor, sales, product launch)
- Pre-pitch checklist
Load this reference when providing detailed advice on pitch content or structure.
## Example Usage Scenarios
**Scenario 1: Early-stage startup seeking seed funding**
- Focus on problem, solution, market opportunity, and team
- Emphasize founder expertise and early traction
- Include clear funding ask and use of funds
**Scenario 2: Growth-stage company creating sales deck**
- Emphasize product features and customer ROI
- Include customer testimonials and case studies
- De-emphasize fundraising, focus on value proposition
**Scenario 3: Product launch presentation**
- Focus on product features and market need
- Include demo or product screenshots
- Emphasize innovation and competitive positioning
## Customization and Extensions
After generating the base deck:
- Users can manually add images, charts, and custom graphics in PoweRelated 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.