CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-quality-gates

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

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Repository

wshobson/agents

Path

plugins/pptx-deck-creation/skills/pptx-quality-gates/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.