Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pitch Deck Creator

ASecurity

Build compelling pitch decks — narrative arc, slide-by-slide structure, and investor-focused storytelling.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill pitch-deck-creator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pitch Deck Creator?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pitch Deck Creator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-pitch-deck-creator/badge)](https://www.skillsdirectory.com/skills/aicodedecode-pitch-deck-creator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: pitch-deck-creator
description: Build compelling pitch decks — narrative arc, slide-by-slide structure, and investor-focused storytelling.
category: business-marketing
---

## Overview

A pitch deck is a story told in 10–15 slides: a painful problem, an inevitable solution, a huge market, traction, and a team that can win. This skill covers the narrative arc, what belongs on each slide, design principles for readability, and how to tailor decks for different audiences (email teaser vs. live pitch vs. partner meeting).

## When to use

- Preparing a seed or Series A fundraise deck
- Pitching at demo days or competitions
- Creating a partnership or sales pitch deck
- Reworking a deck that isn't getting meetings
- Turning a business plan into a visual narrative

- Creating a 3-minute lightning pitch version
- Adapting the deck for strategic partners vs. investors
- Preparing appendix slides for diligence questions
- Creating investor update decks
- Pitching for debt financing
- Presenting at demo days
## Core concepts

**Narrative arc.** Problem → Solution → Why now → Market → Product → Traction → Business model → Competition → Team → Financials → Ask. Each slide earns the next. The arc should work as a story even without a narrator.

**The 10-slide discipline.** Cover, problem, solution, market, product/demo, traction, business model, competition, team, financials + ask. Appendix for details. If you need 30 slides, the story isn't clear yet.

**One idea per slide.** A slide with three messages has zero messages. Headline as a full sentence stating the takeaway ("Churn dropped 40% after onboarding redesign"), visuals as evidence.

**Traction over vision.** Investors fund momentum. Revenue, growth rate, retention, LOIs, pilots, waitlists — lead with proof, follow with projection.

**Design for the back row.** 30pt+ fonts, minimal text (6 lines max per slide), high contrast, one chart per slide with the insight labeled. Decks are visual aids, not documents.

**The ask slide.** How much, what it's for (use of funds), what milestones it buys, and what terms. Vague asks get vague responses.


**The 3-act investor story.** Act 1: the world is broken (problem, viscerally felt). Act 2: we see the future (solution, product, why now). Act 3: we are winning (traction, team, the ask). Investors decide emotionally in Act 1 and justify analytically in Act 3 — both must land.

**Appendix strategy.** Prepare 10–15 backup slides for predictable deep-dives: detailed financials, tech architecture, go-to-market breakdown, hiring plan, unit economics detail. Having them ready signals preparation; volunteering them unprompted signals you cannot prioritize.

**Investor psychology.** Investors pattern-match: they decide in minutes based on team, market, traction, and clarity.
Your deck must survive the 3-minute skim — headlines and visuals carry the story, details support it.
Every slide answers an investor question; every unanswered obvious question is a red flag.
**Traction slide mastery.** Show momentum: revenue growth charts, user growth, key logos, pipeline, and forward indicators.
Lead with your strongest metric — the one number that makes the opportunity obvious.
Vanity metrics (registered users, page views) without engagement context hurt more than help.
**The ask slide.** How much, what terms (if known), use of funds tied to milestones, and what success looks like in 18 months.
Vague asks ("raising $2–5M") signal unfocused thinking — pick a number and justify it.
## Practical workflow

1. **Write the story first.** Draft the narrative as headlines — one sentence per slide. Read them in sequence: does it flow? Is anything missing? Fix the story before touching design.
2. **Gather proof.** For each claim, find the evidence: metrics, screenshots, customer quotes, logos. Claims without proof get cut or softened.
3. **Build the core 10–12 slides.** Problem (make it visceral — a real customer story beats statistics), solution (demo or screenshots), why now (timing/market shift), market (bottom-up sizing), traction (growth chart), business model (unit economics), competition (2x2 matrix), team (relevant wins), financials (3-year summary), ask.
4. **Design for clarity.** Consistent template, restrained color, charts that highlight the insight (annotate the key data point). Remove every element that doesn't serve the headline.
5. **Create versions.** Teaser (8 slides, sendable, no confidential data) → full deck (for meetings) → appendix (deep dives for diligence). Never email the full detailed deck cold.
6. **Rehearse and iterate.** 20-minute pitch, 10-minute Q&A. Record yourself. After each pitch, note which slides sparked questions and which fell flat — iterate weekly during a raise.

**Slide headline test:** cover the visuals and read only the headlines. If they tell the full story, the deck works.


**Pitch rehearsal drill:** deliver the full pitch in 18 minutes (leaving buffer), then have a colleague ask the 10 hardest questions (why will incumbents not crush you? what is your CAC payback?). Record, review, tighten. Repeat until answers are crisp.

**Deck iteration process:** draft → test with 3 friendly investors/advisors → revise → test with 3 more → finalize v1 → track questions asked (every repeated question = a slide to add or fix) → iterate weekly during fundraising.
The deck improves fastest from real investor questions — log every one.
**Demo day adaptation:** 5-minute version (problem, solution, traction, team, ask) → high-energy delivery → memorable one-liner → clear CTA (meetings, not money, at the event).
Demo days are lead generation for meetings, not closings — optimize for booked follow-ups.
## Common pitfalls

- **Walls of text.** If the audience is reading, they're not listening. Slides support the pitch; they aren't the pitch.
- **Leading with the solution.** Without a felt problem, the solution is uninteresting. Earn attention with the pain first.
- **Vanity market slides.** Trillion-dollar TAMs with no path to capture. Show the market you can actually reach and win.
- **Hiding the competition.** A competitive slide that shows you alone in the quadrant insults intelligence. Show real competitors and your genuine edge.
- **No clear ask.** Ending without stating amount, use of funds, and terms wastes the momentum you built.
- **Tiny unreadable charts.** If the back row can't read it, it doesn't exist. Simplify and annotate.
- **Sending the full deck cold.** Unsolicited 25-slide decks get skimmed. Send a teaser; earn the meeting.
- **Reading the slides.** If you are reading, the audience is ahead of you and bored. Slides are cues; you are the presentation.
- **Defensive Q&A.** Arguing with investor questions. Answer directly, acknowledge valid concerns, and show you have thought about them.
- **Too many slides.** 40-slide decks nobody finishes. 12–15 core slides; details in appendix.
- **Hiding weaknesses.** Investors find them anyway — and penalize the hiding more than the weakness. Address proactively with your mitigation plan.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →