Analyzing a reference PPTX for read-only structure, theme

Pptx reference deck analysis

by wshobson · MIT license · ★ 39,857 on GitHub · updated Sep 21

Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.

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

Overview

Inspect a reference deck as design evidence. This skill never copies, clones, or mutates a source deck.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill pptx-reference-deck-analysis -g -a claude-code

Claude Code (degit)

npx degit wshobson/agents/plugins/pptx-deck-creation/skills/pptx-reference-deck-analysis#main ~/.claude/skills/pptx-reference-deck-analysis

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.7 KB

Read SKILL.md here

wshobson/main1 file shown

SKILL.md2.7 KB

Browse every file on GitHub↗

SKILL.md

Show the full text44 lines

pptx-reference-deck-analysis/SKILL.md44 lines · 2.7 KB

PreviewCode

Outline

RawView on GitHub

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.

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

1	---
2	name: pptx-reference-deck-analysis
3	description: "Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection."
4	---
5
6	# PPTX Reference Deck Analysis
7
8	Inspect a reference deck as design evidence. This skill never copies, clones, or mutates a source deck.
9
10	## Contract
11
12	Implement required extraction on demand with a small task-local `python-pptx` script. Capture only the information required for the new deck:
13
14	- compact prompt context: slide count and size, text summaries, shape counts, styles, brand signals, template use, and layout rhythm;
15	- full extraction: `summary`, slides, and read-only `layout_tree` evidence;
16	- folder diagnostics: one result per deck plus a manifest;
17	- style-master analysis: colors, fonts, size distribution, master/layout use, and flow patterns;
18	- derived template catalog: zero-based source indices, layout roles, usable regions, placeholders, visual structures, and constraints.
19
20	## Rules
21
22	- Keep the source deck read-only and independently author every target-slide coordinate.
23	- Use the bundled OOXML utilities only for raw themes, relationships, notes, comments, animations, media, masters, or layouts that high-level extraction cannot expose.
24	- Record inspected parts and parsing exceptions in the analysis manifest.
25	- Do not use extracted content, fonts, images, or proprietary assets in a generated deck without explicit permission and license evidence.
26
27	## OOXML package inspection
28
29	Install `defusedxml` from `requirements.txt` before using the bundled utilities.
30
31	1. Run `scripts/inspect.py <deck.pptx>` for a compact JSON report of slide order, text, theme tokens, relationships, notes, comments, animations, and media.
32	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.
33	3. Run `scripts/unpack.py <deck.pptx> <output-dir>` only when raw-package evidence is necessary.
34	4. Resolve relationship targets relative to the `.rels` owner; never infer slide order from filenames.
35
36	### Safety
37
38	- Never modify a supplied deck or blindly copy package parts into a new deck.
39	- Run the scripts from a trusted workspace; they reject path traversal, symlinks, oversized members, and archive bombs.
40	- Parse untrusted XML with `defusedxml`; do not enable entity expansion, DTD loading, or network access.
41	- Treat theme colors as tokens unless fully resolved against the color scheme.
42
43	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.
44