pptx-quality-gates — Claude Code skill: PPTX checks
Checks and repairs editable PPTX decks for geometry, accessibility, native objects, source lineage, and OOXML package integrity before delivery.
/plugin marketplace add wshobson/agents
/plugin install pptx-deck-creation@claude-code-workflowsWhat pptx-quality-gates does
The skill compares the requested layout with the built PPTX, then reopens the file to inspect slide count, object bounds, hidden slides, and geometry. For production decks, it runs validate_package.py and saves a JSON package report.
Checks cover document language, slide titles, alt text for meaningful images, reading order, table headers, and source references. When a compatible renderer is already available, you can inspect previews for clipping, font fallback, contrast, and crop issues without adding a renderer dependency.
Keep the spec, PPTX, build record, geometry and accessibility audits, package report, and source manifest together. Install this skill when a deck must stay editable and pass delivery checks; it is unnecessary for a presentation that only needs viewing.
What it helps with
- check slide object geometry
- find text overflow and content collisions
- audit presentation accessibility
- verify native editable content
- validate OOXML package integrity
Example prompts for the agent
- Validate this PPTX before delivery and list geometry problems.
- Reopen the deck and check slide titles, alt text, and reading order.
- Run `validate_package.py`, save the JSON report, and repair the reported issues.
How to install pptx-quality-gates
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install pptx-deck-creation@claude-code-workflowsThis installs the whole pptx-deck-creation plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-quality-gates -a claude-code3Manually: put the files in place
~/.claude/skills/pptx-quality-gates/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pptx-quality-gates/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-quality-gates -a codex2Manually: put the files in place
.agents/skills/pptx-quality-gates/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill pptx-quality-gates -a cursor2Manually: put the files in place
.cursor/skills/pptx-quality-gates/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents pptx-quality-gates2Manually: put the files in place
.github/skills/pptx-quality-gates/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/pptx-deck-creation/skills/pptx-quality-gatesManually: put the files in place
.devin/skills/pptx-quality-gates/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about pptx-quality-gates
How do I install pptx-quality-gates in Claude Code?
Run npx skills add wshobson/agents --skill pptx-quality-gates -a claude-code. The skill file will be available at ~/.claude/skills/pptx-quality-gates/SKILL.md.
What does pptx-quality-gates do?
It checks editable PPTX decks for geometry, accessibility, source lineage, native editability, and OOXML package integrity. When a check fails, it guides repairs to the spec or task-local builder before rerunning the checks.
Which platforms support pptx-quality-gates?
The skill supports Claude Code, Codex, and Cursor. Each platform has its own installation command.
Source text
SKILL.md · MIT
--- 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.
© kimtth · MIT · wshobson/agents