/pptx-quality-gates
Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.
One skill from wshobson-agents.
shell
$ npx -y skills add wshobson/agents --skill pptx-quality-gates --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pptx-quality-gates
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.
Stats
Stars38,171
Forks4,092
LanguagePython
LicenseMIT
Ships with wshobson-agents
SKILL.md
pptx-quality-gates.SKILL.md
--- 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.
