agentleFS
agentdynarqagentdynarq/founder-skills/skills/pitch-deck-review/SKILL.md

pitch-deck-review

Skill0 starsChanged 4 months agoMITView on GitHub

Review a startup pitch deck slide by slide against the canonical seed-stage structure, scoring narrative, clarity, and evidence. Use when the user wants feedback on a pitch deck, deck outline, or fundraising narrative, or asks what slides a pitch deck needs.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. lelephi/marketing-agent-skills-for-founders★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never suggest inflating numbers, renaming vanity metrics as traction, or hiding competitors.

    line 47
  2. Distinctive:

    If traction is genuinely strong, recommend leading with it by slide 2 or 3.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Pitch Deck Review

Review pitch decks the way a partner does in the first 3 minutes: fast, skeptical, looking for the one reason to say no.

Input

Accept a PDF, pasted slide text, or an outline. If given a PDF, read it page by page. If the user has no deck yet, flip to building mode and draft the outline below with their content.

The canonical structure

Score the deck against these 10 slides. Missing slides are findings, not necessarily failures; note when a merge is deliberate and fine.

  1. Title: company, one-line description a stranger understands
  2. Problem: who hurts, how much, and why now
  3. Solution: what you built, shown not described (screenshot or demo frame)
  4. Market: bottom-up sizing beats top-down TAM hand-waving
  5. Traction: the strongest slide you have; move it earlier if it is good
  6. Business model: who pays, how much, unit economics if known
  7. Competition: honest landscape; "we have no competitors" is an instant red flag
  8. Team: why these people win this market
  9. Financials / projections: 18-month plan, key assumptions visible
  10. Ask: amount, use of funds, milestones it buys

Review method

For each slide present, report:

  • Score 1-5 for clarity and evidence
  • The skeptic's question: the first thing an investor would push on
  • One concrete fix, not general advice

Then give a deck-level verdict:

  • The narrative in one sentence. If you cannot write it, that is the core problem.
  • The single weakest slide and why it risks losing the room.
  • The 3 changes with the highest impact, ranked.

Rules

  • Judge evidence, not enthusiasm. Flag every claim with no number or proof behind it.
  • Ten slides, roughly one idea per slide. Flag walls of text (over ~30 words on a slide is a finding).
  • Never suggest inflating numbers, renaming vanity metrics as traction, or hiding competitors.
  • If traction is genuinely strong, recommend leading with it by slide 2 or 3.

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.