Pptx Html Fidelity Audit

When you export HTML slide decks to PowerPoint with python-pptx, you get silent layout drift: footers that overflow, italics that vanish, hero slides that stick to the top instead of centering. This skill walks you through a five-step audit workflow that compares the PPTX dump against the source HTML, catalogs the breaks (footer overflow, cropped content, missing em tags, off-rhythm spacing), then re-exports with a cursor-flow layout discipline that enforces a footer rail and refuses to render slides that would bleed. It's built for the specific pain of maintaining visual fidelity across the HTML to PPTX boundary, where every slide has different intrinsic height and hand-picked coordinates quietly fail.

skills.sh installs: 3.3K
GitHub stars: 106.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add nexu-io/open-design --skill pptx-html-fidelity-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

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):

<section class="slide light">
  <div class="chrome">2026 · Q2 review</div>
  <span class="kicker">Pillar 03</span>
  <h2 class="h-xl">Shipping <em>velocity</em> doubled</h2>
  <p class="lead">…</p>
  <div class="foot">page 5 / 14</div>
</section>

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.