← ClaudeAtlas

creating-presentationslisted

Use when the user wants to build a multi-slide HTML presentation styled from a brand preset with a bundled default, or wants an existing deck reviewed, audited, or polished until it is genuinely done. Triggers on requests to create a deck, build slides, turn content into a presentation, or to audit, polish, or make a deck crisp. Includes a two-window presenter view for live sharing in Teams, Zoom, or Meet. For converting a finished HTML deck into editable PowerPoint, see the exporting-presentations-to-pptx skill.
pgoell/pgoell-claude-tools · ★ 0 · Data & Documents · score 68
Install: claude install-skill pgoell/pgoell-claude-tools
# Creating Presentations Multi-slide HTML decks styled from a brand preset, presented straight from the browser through a bundled deck-stage engine, and reviewed to done through a strict convergence loop. HTML is the working medium: fast to iterate, diffable, and exportable to native PowerPoint later without a redesign pass. Building and perfecting are one lifecycle. A new deck flows top to bottom through the sections below; a deck that already exists and only needs review enters directly at "Perfecting the deck". The perfecting loop is opt-in: it burns subagent tokens every round, so it starts only when the user asks for it or accepts the offer. ## Dependencies The decks themselves are dependency-free: self-contained HTML that opens from `file://`. Tools enter only for presenting and perfecting; check for them when those branches start. - A Chromium-based browser (Edge, Chrome, Arc) presents the deck: `BroadcastChannel` sync and the presenter's "Save to deck" (File System Access API) are Chromium-only. The same binary, headless, screenshots slides for the review loop: `chrome --headless --screenshot=slide.png --window-size=1920,1080 --hide-scrollbars <url>` (on Windows the preinstalled `msedge.exe` accepts the same flags). - `uv` serves the deck over HTTP for the hard gates (`uv run python -m http.server 8123 --directory <deck-dir>`); webfonts and `BroadcastChannel` behave differently on `file://` origins. - The perfecting loop needs subagent dispatch (the Workflow tool