Deck publisher

Deck Publisher

Content → a web-native slide deck: keyboard/scroll navigable, responsive, presentable from any device, at a URL — not a .pptx attachment.

Follow the shared flow in the root SKILL.md. Deck-specific craft below.

When to use

• "Make this a deck / slides / a presentation"
• The content will be presented (meeting, pitch, demo) rather than read
• If the user needs a .pptx file specifically, say so and defer to a pptx tool — this skill makes live web decks

Steps

1. Establish the setting. Presented live by the user, or sent to be clicked through alone? A presented deck carries less text per slide (the speaker is the content); a send-ahead deck must stand alone. Ask if unclear — it changes every slide.
2. One idea per slide. Convert the source content into a slide outline first: each slide gets a full-sentence headline that states its point (a reader who only reads headlines should get the whole argument). Show the outline before authoring the deck.
3. Data becomes visuals. Tables of more than a few cells become charts where the design system provides them; walls of bullets become 3–4 short lines max. Anything that can't be cut goes to an appendix slide.
4. Author + lint + approval gate per the shared flow — preview is the slide outline plus any slides with numbers on them.
5. Publish. Return the URL and mention presenter navigation (keyboard/scroll) and that view analytics are attached for send-ahead decks.

Hard rules

• Never exceed the point-per-slide rule to save slide count — more slides beats denser slides.
• The first slide states the ask/conclusion when the deck is persuasive (pitch, proposal); background never comes first.
• Keep the user's numbers exact; rounding for a headline is fine only when the exact figure appears on the same slide or in the appendix.