ClaudeSuperPower
SubmitLog in

pitch-deck

Skill

Build a pitch deck as one self-contained HTML file (keyboard and click navigation, staggered slide-entry animations, a persistent brand mark, cited numbers with real links), write its timed walkthrough narration, and optionally record the walkthrough as video parts that stitch around a demo film. Us

0Media

Install

git clone https://github.com/ooiyeefei/ccc.git ~/.claude/skills/pitch-deck

What is pitch-deck?

Build a pitch deck as one self-contained HTML file (keyboard and click navigation, staggered slide-entry animations, a persistent brand mark, cited numbers with real links), write its timed walkthrough narration, and optionally record the walkthrough as video parts that stitch around a demo film. Use whenever the user asks for a pitch deck, demo-day / hackathon / investor slides, a slide walkthrough video, deck narration, or wants an existing HTML deck polished, re-branded, or recorded. Not for - .pptx slide files (use a pptx skill), the product demo film itself (demo-video), or deciding overall pitch strategy and audience framing (pitch-package).

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~164 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Pitch Deck - one HTML file, narrated, recordable

The deck is the backdrop; the speech carries the pitch. So the deck's job is: one idea per slide, minimal text, numbers that are cited or cut, and navigation reliable enough to drive by hand on stage or by script on camera. One file, no CDN - it must open from disk, on a venue machine, with no network.

Steps

1. Outline: one slide, one idea

Derive the slide list from the pitch story (the pitch-craft skill's storytelling rules apply to structure too). A proven arc to adapt, not worship:

Hook -> what-it-is 101 -> the cost of the status quo -> Reveal (name + throughline) -> test bed / credibility -> the concrete example -> how it works (one flow, end to end) -> "watch it work" (the demo slot) -> the differentiator ("it learns") -> one-more-thing -> roadmap -> architecture -> Close (numbers land again + name).

Appendix slides (anticipated hard questions: safety, "is this really agentic", adoption, commercials) go AFTER the close, are never narrated, and are opened only when a judge asks.

2. Build the single file

Follow references/deck-patterns.md: section-per-slide skeleton, hash-based deep links (#11 starts at slide 11 - the recorder depends on this), data-anim staggered entries, a fixed brand mark in the top-right of every slide, progress bar + counter. Rules that earn their keep: cited or cut (every industry number hyperlinks a real source, verified to load), vector icons never emojis, synthetic-data disclaimers as one corner legend rather than per-slide clutter.

3. Narrate via pitch-craft

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.