Agent skill · writing content · nexu-io
pptx-html-fidelity-audit
Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an HTML slide deck and asks to compare/audit/verify/fix the export — including phrases like "compare ppt with html", "fidelity audit", "fix the pptx", "ppt is cut off", "footer overlap", "italic missing in pptx", "re-export the deck", "pptx-html-fidelity-audit", or any case where a python-pptx → HTML round-trip needs verification or repair. Also trigger when the user shows you a deck.html and a deck.pptx side by side and is debugging visual differences.
Why this skill is useful
Adds an executable script for extracting PPTX content and a structured workflow for auditing fidelity between PPTX and HTML that isn't covered in standard documentation.
What it needs
Requires python installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
PPTX ↔ HTML Fidelity Audit A repeatable workflow for catching the ways a python-pptx export silently drifts from its HTML source — and fixing them with a layout discipline that prevents the same regressions on the next pass. When this skill applies The user has: A source HTML slide deck (typically a single-file deck with <section class="slide"> blocks): A PPTX file generated from that deck via python-pptx (or similar). A suspicion (or visible evidence) that the PPTX doesn't match the HTML — text bleeding into the footer, italic words gone flat, hero slides not centered, sections cropped, tag styling lost. If the user only has one of those two artifacts, this skill doesn't apply yet — first generate the missing one, or ask the user to provide it. Why this is hard (and why a skill helps) PPTX is a fixed-canvas, absolute-positioned medium. HTML is a fluid, flow-based medium. A naive python-pptx export pins each block at hand-picked (top, left) coordinates, which works for the first slide it was tested on and silently fails for every other slide whose content has different intrinsic height. The result is the most common drift modes: 1. Footer overflow — content's top + height crosses into the footer row. 2. Off-canvas content — bottom of last block exceeds 7.5" (16:9 canvas). 3. Italic loss — <em> in HTML never gets run.font.italic = True. 4. Hero slides not centered — vertical-stack slides use MARGINTOP instead of computing center. 5. Box bounds intruding — the text fits, but the shape's bounding box is oversized and visually crosses the rail. 6. Tag/styling loss — colored chrome rows, kicker uppercase tracking, mono-vs-serif assignments quietly fall back to defaults. Every one of these is a layout discipline problem, not a content problem. Once you adopt the discipline, they stop happening. --- Workflow The audit is five steps. Don't skip any of them — the discipline only works if the audit produces a real list of issues to drive the re-export. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/pptx-html-fidelity-audit--22aa7d