PowerPoint Quality Validator

Pptx quality gates

by wshobson · MIT license · ★ 39,857 on GitHub · updated Sep 21

Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.

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

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.

Overview

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

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill pptx-quality-gates -g -a claude-code

Claude Code (degit)npx degit wshobson/agents/plugins/pptx-deck-creation/skills/pptx-quality-gates#main ~/.claude/skills/pptx-quality-gates

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md1.6 KB

Read SKILL.md here

wshobson/main1 file shown

SKILL.md1.6 KB

Browse every file on GitHub↗

SKILL.md

Show the full text29 lines

pptx-quality-gates/SKILL.md29 lines · 1.6 KB

PreviewCode

Outline

RawView on GitHub

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.md to 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.py and 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.

1	---
2	name: pptx-quality-gates
3	description: "Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity."
4	---
5
6	# PPTX Quality Gates
7
8	Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.
9
10	## Workflow
11
12	1. Confirm the spec, builder, PPTX, source manifest, and audit paths.
13	2. Apply `references/audit-checklist.md` to the coordinate contract before building.
14	3. Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
15	4. For production decks, run `pptx-reference-deck-analysis/scripts/validate_package.py` and save the JSON report.
16	5. Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
17	6. When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
18	7. Repair the spec or task-local builder, rebuild, and rerun the same checks.
19
20	## Required artifacts
21
22	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.
23
24	## Pass criteria
25
26	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.
27
28	See `references/audit-checklist.md` for the complete checklist.
29