skills/marketing/pitch-deck/SKILL.md
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.
npx skillsauth add pedronauck/skills pitch-deckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Activate this skill when users request:
Collect necessary information from the user to populate the pitch deck. Use a conversational approach to gather details across the following categories:
Required information:
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:
Organize the gathered information into the standard pitch deck structure:
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:
grep -A 10 "### [Slide Number]. [Slide Name]" references/pitch_deck_best_practices.md
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:
{
"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:
company_nameour_advantages and competitors keys (for two-column layout) or a simple arrayExecute the Python script to create the PowerPoint presentation:
python3 scripts/create_pitch_deck.py pitch_data.json output_filename.pptx
The script will:
.pptx file ready for presentation or further customizationPresent the generated pitch deck location to the user and offer to:
Iteration approach:
The generated pitch deck follows these design principles:
Color Scheme:
Typography:
Layout:
Visual Hierarchy:
For detailed guidance on pitch deck content, structure, and presentation tips, reference:
references/pitch_deck_best_practices.md - Comprehensive guide covering:
Load this reference when providing detailed advice on pitch content or structure.
Scenario 1: Early-stage startup seeking seed funding
Scenario 2: Growth-stage company creating sales deck
Scenario 3: Product launch presentation
After generating the base deck:
Script errors:
python-pptx library is installed: pip3 install python-pptxContent issues:
create_pitch_deck.py: Python script that generates PowerPoint presentations from structured JSON datapitch_deck_best_practices.md: Comprehensive guide on pitch deck content, structure, and design principlestools
Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.
development
Executes real-user QA sessions through public interfaces using personas, journeys, exploratory charters, test tours, edge-case probes, CFR checks, and browser evidence. Reads qa-report artifacts from <qa-output-path>/qa/ when present, captures issues/screenshots/reports under the same output tree, and classifies bugs by user impact. Use when validating a release candidate, migration, refactor, or user-facing change against production-like behavior. Do not use for AI implementation audits, task-status reconciliation, CI gate runs, integration/security/performance templates, or flaky-test triage; use agent-output-audit for those.
development
Transform outside-of-diff review files into properly formatted issue files for a given PR. Use when converting review files from ai-docs/reviews-pr-<PR>/outside/ into issue format in ai-docs/reviews-pr-<PR>/issues/. Automatically determines starting issue number and preserves all metadata (file path, date, status) from original review files. Don't use for inline-diff review files, non-PR review artifacts, or creating GitHub issues directly.
development
Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.