← ClaudeAtlas

exporting-decks-to-pptxlisted

Use when the user wants to export or convert an existing workbench HTML deck into a native, editable PowerPoint file (.pptx) with real text boxes, autoshapes, embedded images, and speaker notes. Triggers on requests like "make a PowerPoint version of this deck" or "export the deck to pptx". For building a new HTML presentation, see workbench:crafting-presentations.
pgoell/pgoell-claude-tools · ★ 0 · Data & Documents · score 70
Install: claude install-skill pgoell/pgoell-claude-tools
# Exporting Decks to PPTX Convert a workbench deck-stage HTML presentation into a fully native, editable PowerPoint file: real text boxes and autoshapes, exact design-token colors, embedded images, and speaker notes carried over. Not screenshots on slides. ## When to use this skill Use when the user asks for a PowerPoint or pptx version of an existing HTML deck: "make a PowerPoint version of presentations/<deck>/", "export this deck to pptx", "I need an editable pptx of these slides". Do not use this skill to build a new presentation; that is `workbench:crafting-presentations`. This skill consumes that skill's output. ## Inputs to gather 1. The deck HTML. Auto-detect the layout: - Single-file deck: a directory containing one `.html` with styles, runtime, and notes inlined. - Multi-file deck: a `slides/` layout with `slides/index.html` plus `slides/slides.css` and the runtime JS. Every `<section>` is one slide; `data-screen-label` names it. A `<script type="application/json" id="speaker-notes">` block holds presenter notes keyed by 1-based slide number. 2. The design tokens (`:root` CSS variables) and per-slide-type layout rules. Read the shared CSS first, then the deck's own inline `<style>` block in the HTML head. Decks override tokens locally, so the inline overrides win; lifting a token from the shared CSS alone will recolor the deck wrongly. 3. Image assets the deck references (headshots, brand SVGs, logos). Output path: for a single-file deck, write next