agentleFS
emotixcoemotixco/claude-skills-founder/skills/pitch-deck/SKILL.md

pitch-deck

Skill796 starsChanged 39 days agoMITView on GitHub

Outline a 12-slide investor pitch deck with a takeaway headline, content, visual, and speaker notes for every slide, plus appendix slides for Q&A. Use when a founder is preparing a deck for a raise, or asks for the content of one slide in it, such as the traction, market size, or competition slide.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-marketing, cold-outreach and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 4 projects that use this

  • vijpatel7Skill

    cold-outreach

    Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.

    Also in 3 projects that use this

  • AnthropicSkill

    contract-review

    Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal agreement.

    Also in 3 projects that use this

  • AnthropicSkill

    content-strategy

    Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.

    Also in 4 projects that use this

  • birne-skSkill

    market-research

    Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

    line 14
  2. Distinctive:

    Create a 12-slide outline.

    line 24
  3. Very specific:

    Every number on a slide comes from the founder, from founder/, or from a linked source.

    line 30
  4. Distinctive:

    Use of funds: 3-4 buckets with % allocation

    line 85
  5. Distinctive:

    When the next round happens

    line 87
  6. Distinctive:

    Numbers to find: every placeholder from the deck, in one list.

    line 98
  7. Distinctive:

    Every headline states a takeaway

    line 101
  8. Distinctive:

    Keep total output under 2000 words.

    line 110

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a pitch deck advisor. You know investors skim, so every slide has to make one point fast.

Input: $ARGUMENTS

Before you start

Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

  • Reads: founder/facts.md, founder/product-brief.md, founder/competitor-matrix.md, founder/pricing-strategy.md, founder/go-to-market.md, founder/metrics-dashboard.md, founder/fundraise-prep.md
  • Needs: what the company does, the stage, how much is being raised, traction numbers (or "none yet"), and the team
  • Saves to: founder/pitch-deck.md

Also ask whether the deck will be presented live or sent ahead. A sent-ahead deck needs more text on each slide. A live deck needs less text and fuller speaker notes.

Instructions

Create a 12-slide outline. For each slide:

  • Headline: one sentence that states the takeaway, not a label. "Market size" is a label. "[N] independent restaurants in the US lose [$X] a year to food waste" is a takeaway.
  • Content: bullets, with the specific data to include
  • Visual: the chart, screenshot, or diagram to use
  • Speaker notes: what to say out loud, conversational (live decks only)

Every number on a slide comes from the founder, from founder/, or from a linked source. When a number is missing, put a bracketed placeholder on the slide and list it under "Numbers to find" at the end.

Slide structure

Slide 1: Title

  • Company name, one-line description, founder name and title
  • The description passes the party test: a non-technical person gets it in 5 seconds

Slide 2: Problem

  • A specific, quantified pain (not "it's hard to...")
  • Who has this problem and how many of them
  • What they do about it today, and why that fails

Slide 3: Solution

  • What the product does, in one sentence
  • 3 capabilities that map to the problem
  • A description of the screenshot or product visual

Slide 4: Product

  • The core user flow in 3-4 steps
  • The moment the user gets value they didn't expect
  • A before and after comparison, if it applies

Slide 5: Market size

  • TAM, SAM, SOM with sources
  • A bottom-up calculation (customers × price), not just "the market is $50B"
  • Why now: what changed that makes this possible or necessary today

Slide 6: Traction

  • Users, revenue, growth rate, retention
  • Pre-revenue: waitlist, LOIs, pilots, engagement
  • The one chart to show and what it plots. If no metric is growing yet, say so and show the strongest evidence of demand instead.

Slide 7: Business model

  • How the company makes money, with actual prices
  • Unit economics: CAC, LTV, LTV/CAC, gross margin, marked as estimates where they are
  • 12-24 month revenue projection with the assumptions stated

Slide 8: Competition

  • A 2x2 with axes chosen carefully, where the company wins honestly
  • Why the position is defensible
  • What the company does that no competitor does

Slide 9: Go-to-market

  • The main acquisition channel and its CAC
  • What's working now
  • What the money changes

Slide 10: Team

  • Why this team wins
  • Relevant achievements, not job titles
  • The key hires this round pays for

Slide 11: The ask

  • How much is being raised
  • Use of funds: 3-4 buckets with % allocation
  • The milestones this money reaches
  • When the next round happens

Slide 12: Closing

  • The vision in one sentence
  • Contact information
  • One data point the investor will remember

After the slides

Appendix: 3-5 backup slides for Q&A, such as the financial model, technical architecture, customer case studies, or a detailed competitive breakdown.

Numbers to find: every placeholder from the deck, in one list.

Checklist: confirm before finishing:

  • Every headline states a takeaway
  • One idea per slide. Two ideas means two slides.
  • Slide body text under 30 words on a live deck
  • The story runs problem, solution, proof, opportunity, team, ask

Rules

  • Specific numbers everywhere. "$0 revenue" is better than "pre-revenue" because it's honest.
  • Front-load the most compelling information.
  • Keep total output under 2000 words.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.