Deck Publisher
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).
Install
$ agentstack add skill-dashaworks-report-skills-deck-publisher ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dashaworks-report-skills-deck-publisher) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dashaworks
- Source: dashaworks/report-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.