Deck Builder

The presentation power-skill. Most people waste hours fighting slide software; the leverage is getting the story and the content right, fast — then formatting is trivial.

What you’ll build

A Skill that takes a source (report, transcript, notes) + an audience and returns:

• The spine — a 6–10 slide narrative, each slide earning its place.
• Per-slide content — headline, 3 supporting points, and the data/visual to show.
• Speaker notes — what to actually say, so the deck presents itself.
• An Artifact — a clean, formatted draft you can refine or export.

How to build it

1. Capture your preferred narrative arc in deck-structure.md (e.g. Situation → Insight → Options → Recommendation → Ask).
2. Tell Claude the audience and the single decision you want from them.
3. Encode it in SKILL.md; have Claude render the draft as an Artifact.

The SKILL.md

---
name: deck-builder
description: Turn source material into a client-ready deck: spine, slide content, and speaker notes.
---

When asked to build a deck:
1. Ask for / confirm: the audience, and the ONE decision or action you want from them.
2. Read the source material (report, transcript, notes, or connected docs).
3. Build the spine using deck-structure.md — every slide must move the audience toward the ask.
4. For each slide: a sharp headline (a claim, not a label), 3 supporting points, and the
   specific chart/visual to show.
5. Add speaker notes: what to say, not a re-read of the slide.
6. Render the result as an Artifact so it's easy to refine and export.

Watch-outs

• Headlines are claims, not labels. “Revenue up 18% on enterprise” beats “Revenue”.
• Anchor every deck to one decision; “informational” decks ramble.
• Keep brand specifics (fonts, palette) in the Skill so output is on-brand by default.