Deck publisher
Claude Code & Codex skills for AI reports, decks and client sharing: publish agent-made research as live tracked web reports, recurring client reports, view-tracked proposals and slide decks via the ReportRoom MCP. Beautiful by default, analytics back to the agent.
npx -y skills add dashaworks/report-skills --skill deck-publisherAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn content into a responsive, presenter-friendly slide deck published at a live URL via ReportRoom. Use when the user says "make this a deck", "turn this into slides", "presentation for", or wants something to present rather than read. Not for long-form documents (use report-publisher) or polishing an existing deck (use report-designer).
SKILL.md
2.2 KB, as published. Nobody here has run it
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
- 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.
- 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.
- 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.
- Author + lint + approval gate per the shared flow — preview is the slide outline plus any slides with numbers on them.
- 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.