Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Inspect a reference deck as design evidence. This skill never copies, clones, or mutates a source deck.
Implement required extraction on demand with a small task-local python-pptx script. Capture only the information required for the new deck:
summary, slides, and read-only layout_tree evidence;Install defusedxml from requirements.txt before using the bundled utilities.
scripts/inspect.py <deck.pptx> for a compact JSON report of slide order, text, theme tokens, relationships, notes, comments, animations, and media.scripts/validate_package.py <deck.pptx> --output <report.json> for malformed XML, broken internal relationships, content-type gaps, duplicate layout links, and orphaned parts.scripts/unpack.py <deck.pptx> <output-dir> only when raw-package evidence is necessary..rels owner; never infer slide order from filenames.defusedxml; do not enable entity expansion, DTD loading, or network access.See references/reference-deck-analysis.md for output shapes, references/reference-deck-analysis-patterns.md for documentation-only patterns, and references/ooxml-parsing.md for package part maps.
wshobson/agents
9c61ab2
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.