Skip to content
Back to skills

Vc Pitch Deck

ASecurity

Create, review, or revise investor decks and individual slides, including send-ahead, presented, and demo-day variants. vc-strategy owns fundraising strategy/narrative; vc-outreach owns investor outreach and meetings.

  • 617 stars
  • 0 votes
  • 0 copies
  • 9 views
  • Added September 5, 2026
documentation

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add pedronauck/skills --skill vc-pitch-deck --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vc Pitch Deck?

Add the live security badge to your README. It updates with every re-scan.

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

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

Download with Pro
SKILL.md
---
name: vc-pitch-deck
description: "Create, review, or revise investor decks and individual slides, including send-ahead, presented, and demo-day variants. vc-strategy owns fundraising strategy/narrative; vc-outreach owns investor outreach and meetings."
---

# 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.

Files in this skill

  • SKILL.md2 KB
  • references/proof-slides.md11.2 KB
  • references/sequences-and-variants.md10.3 KB
  • references/slide-anatomy.md8.2 KB
  • references/teardown-rubric.md6.9 KB

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.