AutoGineer
Generated banner for PPTX Quality Gates
Generated logo for PPTX Quality Gates

PPTX Quality Gates

Seth HobsonCommunityCreated by kimtthDistributed by Seth Hobson

  • Skill
  • Review and audit
  • Documents and content
  • MIT
  • No issues found
Download ZIP

From the author

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

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

PPTX Quality Gates provides a systematic approach to verifying PowerPoint presentations before final delivery. It focuses on ensuring that decks meet specific technical requirements, including correct geometry, native editability, accessibility standards, and OOXML package integrity. The skill guides users through a pre-build audit of content and design constraints, followed by a post-build validation process to identify and resolve structural or formatting issues.

What it does

  • Validates PPTX files for geometry, accessibility, and OOXML package integrity.
  • Checks for content collisions, text overflows, and proper type scaling.
  • Ensures native editability of titles, labels, charts, and explanations.
  • Verifies source lineage for claims within the presentation.
  • Provides a structured checklist for pre-build and post-build inspection.
  • Facilitates the documentation of exceptions for slide and object IDs.

When to use it

  • Before delivering a generated PPTX file.
  • When verifying that presentation content adheres to specific layout and design constraints.
  • During the debugging of malformed XML or broken relationships in a presentation package.
  • When ensuring that accessibility features like alt text and reading order are correctly implemented.

Advantages

  • Reduces errors in presentation geometry and layout.
  • Ensures consistent accessibility standards across slides.
  • Maintains native editability of presentation objects.
  • Provides a clear audit trail for any documented exceptions.

Usage examples

“Audit this PPTX deck for geometry and accessibility.”
The agent performs a check against the audit checklist, identifying any content collisions, text overflows, or missing accessibility metadata, and provides a report for necessary repairs.
“Validate the OOXML package integrity for my presentation.”
The agent inspects the package for malformed XML, broken relationships, or content-type gaps, reporting any errors that require manual or automated correction.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/pptx-quality-gates/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip pptx-quality-gates.zip -d .agents/skills

Documentation by kimtth

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.

Files

references/audit-checklist.md

PPTX Manual Audit Checklist

Before build

  1. Content collisions: content bboxes must not overlap: A.x < B.x + B.w && B.x < A.x + A.w && A.y < B.y + B.h && B.y < A.y + A.h.

  2. Text capacity: shorten, resize, or split likely overflows; halve estimated characters-per-line for CJK/full-width text.

  3. Type scale: content text is at least 9 pt.

  4. Design context: summary.design_context names a style lock or approved source. Reject default-theme, plain title-and-bullet output unless explicitly requested.

  5. Layout policy: content stays within safe margins and above the footer rail; only layout_design may be full bleed.

  6. Containment: children fit their parent groups and on-shape text respects inner padding.

  7. Tables: widths sum to the table bbox, wrapped text fits, and long tables are split.

  8. Native editability: titles, labels, values, charts, and explanations remain native objects; images are support only.

  9. Lineage: sourced claims have a resolvable source ID, locator, claim type, and verification status.

  10. Positive geometry: every object has positive dimensions; normalize line endpoints before build.

After build

  1. Reopen the package and compare actual slide count, bounds, hidden-slide state, and requested geometry with the specification.

  2. Check accessible titles, language, reading order, meaningful-image alt text, and table headers.

  3. Run the OOXML package validator. Fix malformed XML, broken relationships, content-type gaps, and duplicate layout links; document any accepted warnings.

  4. When a compatible renderer is already installed, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not introduce a renderer dependency.

Delivery requires all checks to pass or each exception to identify slide ID, object ID, reason, owner, and review date.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
kimtth
Publisher
Seth Hobson (Community)
Distributed by
Seth Hobson
Source
wshobson/agents · plugins/pptx-deck-creation/skills/pptx-quality-gates · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by kimtth or Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pptx-quality-gates.zip