agentleFS
ooiyeefeiooiyeefei/ccc/skills/pitch-deck/SKILL.md

pitch-deck

Skill497 starsChanged 11 months agoMITView on GitHub

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

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Before building, ask whether the company logo and a copyright/distribution notice belong in the deck or recording, whose logo is …

    line 14

“Common” is measured: kept by at least 6 in 10 of the 20 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

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

Before building, ask whether the company logo and a copyright/distribution notice belong in the deck or recording, whose logo is authorised, and the exact notice wording. Record the choice with the outline.

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

Hand the slide list to the pitch-craft skill for the walkthrough script (per-slide timestamp windows, recorded register). A deck changes topic every few slides, and a viewer who is not told where the talk is going feels every jump: where a section changes, the narration says so before the slide does (pitch-craft's transitions), and the close lands the throughline, then the ask for customers or investors, or the name for judges. If the deck will also be presented live, have pitch-craft write the LIVE variant separately (team intro after the hook, stage cues, trim points) - the two registers do not interchange.

4. Record the walkthrough (optional)

Follow references/deck-recording.md: per-slide HOLD durations derived from the narration windows, recorded in two parts around the demo slot (Part A ends paused on the demo slide, Part B fresh-loads after it). The recording harness lives in the demo-video skill (demo-video/scripts/record_template.py) - single source of truth; this skill only contributes the deck-specific driver (click #next, hold per window). The walkthrough takes the same voice, music bed and master as the demo film it wraps, so the stitched film sounds like one piece (demo-video's references/soundtrack.md).

5. Publish and verify

Serve locally, or publish (htmldrop / static host) if a link is needed. Then actually click through every slide checking: entry animations fire, no broken assets, citations open, the brand mark sits on every slide, and the demo embed (if any) loads. A deck you haven't paged through end-to-end is not done. For a shared file or recording, verify that the approved rights line and company logo appear in their agreed placement (demo-video's references/structure.md).

References

  • references/deck-patterns.md - the single-file skeleton: nav, animations, brand mark, citations, demo-slot slide, appendix pattern.
  • references/deck-recording.md - HOLDS from narration windows, the two-part split around the demo, stitching order.

Download now (ZIP)

  • Other versions22 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 22

    1. anthropics/financial-services★ 41ksame name
    2. anthropics/financial-services-plugins★ 41ksame name
    3. emotixco/claude-skills-founder★ 725same name
    4. shawnpang/startup-founder-skills★ 331same name
    5. SanketSapkal/founder-skills★ 10same name
    6. astDeniss/business-skills★ 8same name
    7. Maudeunfledged834/startup-founder-skills★ 8same name
    8. ARCASSystems/FounderOS★ 7same name
    9. The-Utopia-Studio/skills★ 6same name
    10. getedgehq/skills★ 5same name

    12 more not listed

    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.

  • Used alongsideProjects 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 3 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

    • nicolas-webdevSkill

      landing-page

      Architecture and copywriting framework for high-converting landing pages. Use when building landing pages, sales pages, product pages, or lead capture pages. Follows a proven 8-section structure optimized for conversions.

      Also in 4 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 3 projects that use this

  • In this repository17 other files it gives its agents.

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.