/pptx-quality-gates
Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.
Claude Code
$ npx -y skills add wshobson/agents --skill pptx-quality-gates --agent claude-code
Codex
$ npx skills add wshobson/agents --skill pptx-quality-gates -a codex -y
Cursor
$ npx skills add wshobson/agents --skill pptx-quality-gates -a cursor -y
Gemini CLI
$ npx skills add wshobson/agents --skill pptx-quality-gates -a gemini-cli -y
GitHub Copilot
$ npx skills add wshobson/agents --skill pptx-quality-gates -a github-copilot -y
OpenCode
$ npx skills add wshobson/agents --skill pptx-quality-gates -a opencode -y
Windsurf
$ npx skills add wshobson/agents --skill pptx-quality-gates -a windsurf -y
SKILL.md
pptx-quality-gates.SKILL.mdname: 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.
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.
Read more
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.
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.
Use one collection of plugins, agents, skills, and commands across Claude Code, OpenAI Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot, and Pi. A harness is the coding tool that loads and runs the components.
Other skills on agents.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about pptx-quality-gates.
- Which coding agents can use pptx-quality-gates?
- pptx-quality-gates installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

