mcpField
V
vc-pitch-deck

vc-pitch-deck

github.com/pedronauckDocuments64490 installsUpdated 1w ago
Repository

About vc-pitch-deck

A skill for creating or revising venture-capital pitch decks from supplied narratives and evidence. It guides slide selection, story structure, evidence checks, and review while avoiding unsupported claims.

Key features

  1. 01Selects slides for the intended story
  2. 02Structures and edits slide content
  3. 03Checks evidence in metrics and financial slides
  4. 04Reviews story and changed slides
  5. 05Flags unresolved evidence gaps

Use cases

  1. 01Drafting a new fundraising deck
  2. 02Revising selected slides in an existing deck
  3. 03Preparing metrics and financial slides
  4. 04Reviewing a deck before sharing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pedronauck/skills --skill vc-pitch-deck

After installing, type/vc-pitch-deckin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
proof-slides.md
sequences-and-variants.md
slide-anatomy.md
teardown-rubric.md

Details

From the project README

VC Pitch Deck

Create or improve the requested deck artifact. For an existing deck or one slide, work from the supplied narrative and facts; do not restart a full fundraising strategy exercise.

  1. Resolve the audience, format, and intended decision from context. Identify the evidence available and consequential missing facts.
  2. For a new deck, use the relevant sequence in references/sequences-and-variants.md; choose the slides the story needs, not a fixed count or five separate variants.
  3. Draft/edit the affected slides using their sections in references/slide-anatomy.md. Keep the opening concrete, headlines coherent, and each slide legible. Word counts and one-visual rules are format heuristics, not automatic failures.
  4. For metrics, market, financials, or ask slides, use references/proof-slides.md: source numbers, label period/unit, distinguish facts from assumptions, and make the ask explicit. Verify current benchmarks before using them as market evidence.
  5. Use the relevant part of references/teardown-rubric.md: a quick skim and headline read for the story, then inspect weak/changed slides. A full slide-by-slide teardown belongs to a full review request. Fix material issues without endless cosmetic passes.
  6. Deliver the requested editable content and/or exported PDF, with unresolved evidence gaps. Add appendix material for real objections; no minimum appendix count or daily refinement quota. Publishing/sending requires separate authorization unless already provided.

For devtools/AI-infra positioning, use the canonical ../vc-strategy/references/devtools-positioning.md when installed; otherwise work from the supplied product evidence and verify missing facts. Do not invent a moat, growth channel, or pedigree claim to fill a slide.

Comments

Markdown supported