PPTX Presentation Assistant

What it solves

When generating PowerPoint files, the hard part is often not exporting a .pptx, but controlling content extraction, template reuse, and visual quality. Text can be scattered across XML layers, placeholder text can survive editing, layouts can feel generic, colors and spacing can be inconsistent, and the final deck still needs slide-by-slide review. This skill treats PPTX files as inspectable, editable, and renderable artifacts rather than a black-box export.

How it works

The workflow branches by task. For reading or analysis, it uses python -m markitdown presentation.pptx to extract text and inspect content structure. For template editing, it starts by analyzing the template with thumbnail.py, then moves through unpacking, manipulating slides, editing content, cleaning, and repacking. This path is useful when a brand template or reference deck already exists. For creating from scratch, it uses pptxgenjs, which is the right option when no template is available.

The design guidance is concrete: choose a topic-specific palette, keep one dominant color, maintain dark/light contrast, and repeat a visual motif across slides. Every slide should include an image, chart, icon, shape, or other visual element instead of relying on plain bullets. It also covers typography, font pairing, size hierarchy, margins, spacing, and common mistakes such as centered body text, low contrast, random spacing, and title underline accents.

Limits to watch

The skill makes QA mandatory: after generating slides, convert them to images, list issues, fix them, and re-verify affected slides. When working with templates, check for leftover placeholder text. It depends on local tools such as markitdown[pptx], Pillow, pptxgenjs, LibreOffice, and Poppler, so final rendering depends on the environment and source template quality.