pptxlisted

# pptx skill **Purpose**: Turn Markdown into presentable `.pptx` decks in one command, convert decks to PDF or thumbnail grids for review, and give the agent a safe path to edit existing `.pptx` files. Inline `pptxgenjs` or `python-pptx` coding regresses on layout, padding, and typography every time; wrapping the common operations in scripts removes that variance. ## 1. Red Flags (Anti-Rationalization) **STOP and READ THIS if you are thinking:** - "I'll hand-write pptxgenjs calls for this small deck." → **WRONG**. Layout, padding, and bullet indent defaults in `md2pptx.js` encode lessons learned across many decks. Inline code reinvents those and forgets half. - "I'll pack 7 bullets into a slide, the user wants information density." → **WRONG**. 3–5 bullets max. Dense slides are unreadable. See [references/design-principles.md](references/design-principles.md). - "Thumbnails are optional, I don't need to review visually." → **WRONG**. Structural validators do not catch white-on-white text, clipped content, or placeholder leftovers. Always render `pptx_thumbnails.py` before calling the deck done. - "I'll edit the .pptx with python-pptx, it's simpler." → **WRONG** for anything touching the slide master, theme, or relationships. Use `office/unpack.py` + hand-edit + `office/pack.py` for those — see [references/editing-workflow.md](references/editing-workflow.md). ## 2. Capabilities - Convert a `.pptx`/`.pptm` deck **into structured Markdown** via `pptx2md.py`: one `## Slide