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.
SkillScore55Maintained
Automatic
◆Doc Ops pack
Last verified 7/28/2026
What it changes
Passed 9 of 17 test cases with the skill, and 2 of 17 without it.
Without skill9%
With skill55%
10 fixed2 passed either way10 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+141%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 7/28/2026v112 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md238 lines7 filesincludes scripts
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:
Footer overflow — content's top + height crosses into the footer row.
Off-canvas content — bottom of last block exceeds 7.5" (16:9 canvas).
Italic loss — <em> in HTML never gets run.font.italic = True.
Hero slides not centered — vertical-stack slides use MARGIN_TOP instead of computing center.
Box bounds intruding — the text fits, but the shape's bounding box is oversized and visually crosses the rail.
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.