pptx-reference-deck-analysis
Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.
Install
npx skills add https://github.com/wshobson/agents/tree/main/plugins/pptx-deck-creation/skills/pptx-reference-deck-analysis
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
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 Reference Deck Analysis
Inspect a reference deck as design evidence. This skill never copies, clones, or mutates a source deck.
Contract
Implement required extraction on demand with a small task-local python-pptx script. Capture only the information required for the new deck:
- compact prompt context: slide count and size, text summaries, shape counts, styles, brand signals, template use, and layout rhythm;
- full extraction:
summary, slides, and read-onlylayout_treeevidence; - folder diagnostics: one result per deck plus a manifest;
- style-master analysis: colors, fonts, size distribution, master/layout use, and flow patterns;
- derived template catalog: zero-based source indices, layout roles, usable regions, placeholders, visual structures, and constraints.
Rules
- Keep the source deck read-only and independently author every target-slide coordinate.
- Use the bundled OOXML utilities only for raw themes, relationships, notes, comments, animations, media, masters, or layouts that high-level extraction cannot expose.
- Record inspected parts and parsing exceptions in the analysis manifest.
- Do not use extracted content, fonts, images, or proprietary assets in a generated deck without explicit permission and license evidence.
OOXML package inspection
Install defusedxml from requirements.txt before using the bundled utilities.
- Run
scripts/inspect.py <deck.pptx>for a compact JSON report of slide order, text, theme tokens, relationships, notes, comments, animations, and media. - Run
scripts/validate_package.py <deck.pptx> --output <report.json>for malformed XML, broken internal relationships, content-type gaps, duplicate layout links, and orphaned parts. - Run
scripts/unpack.py <deck.pptx> <output-dir>only when raw-package evidence is necessary. - Resolve relationship targets relative to the
.relsowner; never infer slide order from filenames.
Safety
- Never modify a supplied deck or blindly copy package parts into a new deck.
- Run the scripts from a trusted workspace; they reject path traversal, symlinks, oversized members, and archive bombs.
- Parse untrusted XML with
defusedxml; do not enable entity expansion, DTD loading, or network access. - Treat theme colors as tokens unless fully resolved against the color scheme.
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.
Files (agents)
-
references
-
ooxml-parsing.md 1.1 KB
Loading… -
reference-deck-analysis-patterns.md 1.2 KB
Loading… -
reference-deck-analysis.md 1.5 KB
Loading…
-
-
scripts
-
inspect.py 5.9 KB
Loading… -
unpack.py 3 KB
Loading… -
validate_package.py 9.5 KB
Loading…
-
-
requirements.txt 19 B
Loading… -
SKILL.md 2.7 KB
--- name: pptx-reference-deck-analysis description: "Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection." --- # PPTX Reference Deck Analysis Inspect a reference deck as design evidence. This skill never copies, clones, or mutates a source deck. ## Contract Implement required extraction on demand with a small task-local `python-pptx` script. Capture only the information required for the new deck: - compact prompt context: slide count and size, text summaries, shape counts, styles, brand signals, template use, and layout rhythm; - full extraction: `summary`, slides, and read-only `layout_tree` evidence; - folder diagnostics: one result per deck plus a manifest; - style-master analysis: colors, fonts, size distribution, master/layout use, and flow patterns; - derived template catalog: zero-based source indices, layout roles, usable regions, placeholders, visual structures, and constraints. ## Rules - Keep the source deck read-only and independently author every target-slide coordinate. - Use the bundled OOXML utilities only for raw themes, relationships, notes, comments, animations, media, masters, or layouts that high-level extraction cannot expose. - Record inspected parts and parsing exceptions in the analysis manifest. - Do not use extracted content, fonts, images, or proprietary assets in a generated deck without explicit permission and license evidence. ## OOXML package inspection Install `defusedxml` from `requirements.txt` before using the bundled utilities. 1. Run `scripts/inspect.py <deck.pptx>` for a compact JSON report of slide order, text, theme tokens, relationships, notes, comments, animations, and media. 2. Run `scripts/validate_package.py <deck.pptx> --output <report.json>` for malformed XML, broken internal relationships, content-type gaps, duplicate layout links, and orphaned parts. 3. Run `scripts/unpack.py <deck.pptx> <output-dir>` only when raw-package evidence is necessary. 4. Resolve relationship targets relative to the `.rels` owner; never infer slide order from filenames. ### Safety - Never modify a supplied deck or blindly copy package parts into a new deck. - Run the scripts from a trusted workspace; they reject path traversal, symlinks, oversized members, and archive bombs. - Parse untrusted XML with `defusedxml`; do not enable entity expansion, DTD loading, or network access. - Treat theme colors as tokens unless fully resolved against the color scheme. 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.