Pptx Reference Deck Analysis
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add pptx-reference-deck-analysisWho is stuck, and on what
Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.
The whole source
Frontmatter — 2 properties
| 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. |
| 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 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 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 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Research Review via External Reviewer Backend (ultra reasoning)Get a deep critical review of research from an external reviewer backend (Codex or manual). Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.●····●38/40Training CheckPeriodically check WandB metrics during training to catch problems early (NaN, loss divergence, idle GPUs). Avoids wasting GPU hours on broken runs. Use when training is running and you want automated health checks.●····●37/40Changelog AutomationAutomate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.◐····●36/40Hermes Tweet> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.◐····●36/40