pptx-reference-deck-analysis
/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.
- Author
- wshobson ↗
- Repository
- agents ↗
- Licence
- MIT
- Last repository change
- 17.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 3
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 3 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/inspect.py, scripts/unpack.py, scripts/validate_package.py
What it does and when to use it
Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.
Original author description
Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.
How it works
- Contract
- Rules
- OOXML package inspection
SKILL.md preview
--- 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.
Files in this package (8)
- SKILL.md 3 KB
- requirements.txt 1 KB
- references/ooxml-parsing.md 1 KB
- references/reference-deck-analysis-patterns.md 1 KB
- references/reference-deck-analysis.md 2 KB
- scripts/inspect.py 6 KB
- scripts/unpack.py 3 KB
- scripts/validate_package.py 9 KB
Versions
The database has no other skills named pptx-reference-deck-analysis.
Database snapshot: 13.11.2026 · package version 6f03d0abeef2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90pptx-quality-gates
Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity. - 100pptx
PPT演示文稿创建与编辑工具。支持从零新建(html2pptx)、基于模板创建、编辑现有PPT(OOXML)、幻灯片重排与文本替换。本技能应在用户需要制作、修改或分析.pptx文件时使用。 - 90pptx-deck-context
Use when preparing the narrative, sources, and design context for a new editable PPTX deck. - 90ooxml-provenance
Check where claims in a .docx, .pptx or .xlsx came from and whether they are still current, using the embedded Agentic OOXML sources part and claim hashes. Use when asked whether numbers or statements in a document are up to date, sourced, or stale after the underlying content changed. - 100ooxml-edit
Propose and apply changes to the Agentic OOXML knowledge parts of a .docx, .pptx or .xlsx (agents, design, intent, sources) without touching native document content. Use when the user asks to record editing rules, design notes, intent or source claims in the file, or to refresh stale source claims. - 100pptx-profile
STEP 1 of the PPTX-from-layouts pipeline. Profile a PowerPoint template to discover its real slide-master layouts and emit a layout catalog + render config. Use when the user wants to "use my own PowerPoint template", "see what layouts my deck has", "onboard a template",…