pptx-quality-gates
wshobson/agents
Validate and repair PPTX decks for geometry, accessibility, editability, and package integrity.
What is pptx-quality-gates?
Quality-assurance skill for PPTX generation pipelines. Use before delivering a generated deck to catch geometry errors, accessibility issues, native editability problems, and OOXML package corruption. Treats deterministic failures as repair work rather than exceptions.
- Validate slide geometry, bounds, and layout against coordinate contracts
- Check accessibility: document language, slide titles, alt text, reading order, table headers
- Verify native editability of text and content objects
- Inspect OOXML package integrity using automated validation scripts
- Compare generated slide count and hidden slides against spec
- Audit source lineage and document references
How to install pptx-quality-gates
npx skills add https://github.com/wshobson/agents --skill pptx-quality-gates- A PPTX file to validate
- Spec and builder documentation for the deck
- Source manifest and audit paths
- Python environment for running validate_package.py script
How to use pptx-quality-gates
- 1.Confirm the spec, builder, PPTX file, source manifest, and audit paths are available
- 2.Apply the audit checklist to the coordinate contract before building
- 3.Reopen the generated PPTX and compare slide count, bounds, hidden slides, and geometry against the layout tree
- 4.Run validate_package.py and save the JSON report for production decks
- 5.Check document language, slide titles, alt text, reading order, table headers, and source references
- 6.Inspect previews for clipping, font fallback, contrast, and hierarchy if a compatible renderer is available
- 7.Repair the spec or builder if issues found, rebuild, and rerun all checks
Use cases
- Before delivering auto-generated presentation decks to stakeholders
- Catching geometry collisions and text overflow in programmatically-built slides
- Ensuring accessibility compliance in bulk-generated presentations
- Validating that content remains editable after generation, not locked as images
- Detecting package corruption or malformed OOXML before distribution
- Presentation automation engineers
- QA teams validating generated decks
- Accessibility compliance reviewers
- PPTX generation pipeline owners
pptx-quality-gates FAQ
Treat deterministic failures as repair work: update the spec or task-local builder, rebuild the PPTX, and rerun the same validation checks.
No. Only inspect previews if a compatible renderer is already available; do not add a renderer dependency just for validation.
Keep the spec, PPTX, build record, geometry audit, accessibility audit, package report, and source manifest together for traceability.
Zero content collisions, text overflows, unsafe content bounds, invalid geometry, and package-integrity errors. Meaningful content must remain native editable objects.
Slide content must be editable objects (text, shapes, tables) rather than locked images or flattened content.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
name: pptx-quality-gates description: "Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity."
PPTX Quality Gates
Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.
Workflow
- Confirm the spec, builder, PPTX, source manifest, and audit paths.
- Apply
references/audit-checklist.mdto the coordinate contract before building. - Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
- For production decks, run
pptx-reference-deck-analysis/scripts/validate_package.pyand save the JSON report. - Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
- When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
- 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.
Related skills
More from wshobson/agents and the wider catalog.
pptx-reference-deck-analysis
Analyze reference PowerPoint decks for structure, theme, and layout without copying or modifying them.
pptx-slide-specification
Author coordinate-explicit JSON specifications for editable PPTX decks with precise layout control.
pptx-visual-assets
Select and place approved icons, images, SVGs, and diagrams in PowerPoint decks while preserving editability.
preference-optimization
Align fine-tuned models with preference data using DPO, ORPO, KTO, or SimPO.
projection-patterns
Build read models and projections from event streams for CQRS and event-sourced systems.
prometheus-configuration
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications.