mcpField
P
pptx-quality-gates

pptx-quality-gates

github.com/wshobsonDocuments41.9k2.7k installsUpdated 2w ago
Repository

About pptx-quality-gates

A pre-delivery review skill for generated PowerPoint decks. It defines repeatable checks for geometry, content, accessibility, package integrity, and rendered previews, with repair and rerun guidance.

Key features

  1. 01Specification and artifact path checks
  2. 02Slide bounds and geometry audits
  3. 03Accessibility and reading-order checks
  4. 04Package integrity report for production decks
  5. 05Preview checks when a renderer is available
  6. 06Rebuild and rerun after repairs

Use cases

  1. 01Auditing a generated deck before delivery
  2. 02Finding overflow, clipping, or content collisions
  3. 03Checking image alt text and reading order
  4. 04Recording exceptions and required audit artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wshobson/agents --skill pptx-quality-gates

After installing, type/pptx-quality-gatesin Claude Code to confirm it loaded.

Bundled filesreferences/audit-checklist.md

Details

From the project README

PPTX Quality Gates

Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.

Workflow

  1. Confirm the spec, builder, PPTX, source manifest, and audit paths.
  2. Apply references/audit-checklist.md to the coordinate contract before building.
  3. Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
  4. For production decks, run pptx-reference-deck-analysis/scripts/validate_package.py and save the JSON report.
  5. Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
  6. When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
  7. Repair the spec or task-local builder, rebuild, and rerun the same checks.

Required artifacts

Keep the spec, PPTX, build record, geometry audit, accessibility audit, package report, and source manifest together. Report any documented exception with slide ID, object ID, owner, reason, and review date.

Pass criteria

Zero content collisions, text overflows, unsafe content bounds, invalid positive geometry, and package-integrity errors. Meaningful slide content must remain native editable objects; images support rather than replace it.

See references/audit-checklist.md for the complete checklist.

Comments

Markdown supported