ClaudeSuperPower
SubmitLog in

pitch-package

Skill

The step-back skill for pitching as a person - given an audience (hackathon judges, VCs, investors, customers) and a time slot, it budgets the slot, decides what to build or reuse (deck, demo video, live speech), and orchestrates the pitch-deck, demo-video, and pitch-craft skills into one rehearsed

0Media

Install

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

What is pitch-package?

The step-back skill for pitching as a person - given an audience (hackathon judges, VCs, investors, customers) and a time slot, it budgets the slot, decides what to build or reuse (deck, demo video, live speech), and orchestrates the pitch-deck, demo-video, and pitch-craft skills into one rehearsed package with a stitch plan, Q&A prep, and a day-of checklist. Use whenever the user says they need to pitch, present, or demo at a hackathon or demo day, to investors or a customer, mentions an N-minute slot, or asks to "prepare the whole pitch" end to end. Not for - a single artifact in isolation (call pitch-deck, demo-video, or pitch-craft directly) or written-only submission forms.

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

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

Documentation

README · ~3 min read

Pitch Package - the whole performance

A pitch is one argument delivered through three instruments: the deck (setup), the demo (proof), and the speaker (trust). The demo is the proof; the deck is the setup. This skill's job is sequencing and budget, so the instruments never fight each other. Two rules govern everything: interview before you build, and budget the slot first.

Phase 1 - Interview before you build

STOP: produce no artifacts in this phase. Ask (adapting to what's already known):

  1. Audience: hackathon judges, VCs, or a customer? What do they explicitly judge or care about (rubric, thesis, their own pain)?
  2. Slot: total minutes? Is Q&A inside or after it?
  3. Inventory: what already exists - working product? demo video? deck? scripts? Reuse beats rebuild.
  4. Demo mode: live product on stage (higher wow, higher risk) or recorded film (deterministic)? Default to recorded unless the live path has been rehearsed with a fallback.
  5. Speakers: who talks, and are there real credentials to weave into the intro?
  6. Constraints: venue machine? offline? projector resolution? phone-as-teleprompter?

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.