pptx-quality-gates

Validates and repairs PPTX decks for geometry, accessibility, editability, and OOXML package integrity.

39.3k|4.2k|Updated Jul 24, 2025
One-click install
npx skills add https://github.com/wshobson/agents --skill pptx-quality-gates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pptx-quality-gates
Source: https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-quality-gates
Command: npx skills add https://github.com/wshobson/agents --skill pptx-quality-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generated PowerPoint decks often ship with overlapping content, text overflow, broken OOXML packages, missing alt text, and non-editable content baked into images. This Skill provides a deterministic audit-and-repair workflow that catches these defects before delivery.

Core Features & Use Cases

  • Geometry and Layout Auditing: Checks content collisions, text capacity, safe margins, containment, and positive dimensions against the layout specification.
  • Accessibility and Editability Checks: Verifies slide titles, document language, reading order, meaningful-image alt text, table headers, and that content remains native editable objects.
  • OOXML Package Validation: Runs a package validator to detect malformed XML, broken relationships, content-type gaps, and duplicate layout links, saving a JSON report.
  • Use Case: After generating a 40-slide production deck from a spec, run this Skill to compare actual slide bounds against the layout tree, fix overflows, validate the package, and produce a documented audit trail with any exceptions.

Quick Start

Validate the generated PPTX deck against its spec and repair any geometry, accessibility, or package-integrity failures before delivery.

Frequently Asked Questions about pptx-quality-gates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How to check PowerPoint accessibility requirements programmatically?

Check document language, slide titles, reading order, meaningful-image alt text, and table headers in the reopened package. Each failure must be repaired or documented as an exception with slide ID, object ID, owner, reason, and review date.

What causes text overflow in generated PPTX slides?

Overflow happens when estimated text exceeds shape capacity, especially with CJK or full-width characters where characters-per-line estimates should be halved. Fix it by shortening text, resizing shapes, or splitting content, keeping content text at least 9 pt.

Does PPTX validation require a rendering engine?

No. Visual preview inspection for clipping, font fallback, contrast, and crop is optional and only performed when a compatible renderer is already installed. The workflow explicitly avoids adding a renderer dependency.

When should images be used instead of native PPTX objects?

Images should only support content, never replace it. Titles, labels, values, charts, and explanations must remain native editable objects so the deck stays editable; decks that bake content into images fail the editability gate.