Claude Cursor Skill

pptx-quality-gates

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

LLM Mart · 0 points · 14 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download wshobson-agents-plugins_pptx-deck-creation_skills_pptx-quality-gates-554237f.zip · 2 KB

wshobson/agents 39771 4241 forks MIT Updated 11d ago

Part of wshobson/agents — 170 skills

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-quality-gates

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart

Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

PPTX Quality Gates

Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.

Workflow

Confirm the spec, builder, PPTX, source manifest, and audit paths.
Apply references/audit-checklist.md to the coordinate contract before building.
Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
For production decks, run pptx-reference-deck-analysis/scripts/validate_package.py and save the JSON report.
Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
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 (agents)

references

audit-checklist.md 1.8 KB

# 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

11. Reopen the package and compare actual slide count, bounds, hidden-slide state, and requested geometry with the specification.
12. Check accessible titles, language, reading order, meaningful-image alt text, and table headers.
13. Run the OOXML package validator. Fix malformed XML, broken relationships, content-type gaps, and duplicate layout links; document any accepted warnings.
14. 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.

SKILL.md 1.6 KB

---
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.