Pptx Reference Deck Analysis

PPTX Reference Deck Analysis

Use this skill when you need read-only analysis of a reference PPTX, extracted deck structure, style-master signals, deck diagnostics, or package inspection while keeping the repository lightweight.

Allowed Directories

• references/ for static documentation only

Do not add other directories under this skill, and do not ship importable Python (or other runtime) code in this skill. Historical Python snippets may live under references/ as documentation-only examples, but there are no bundled scripts or importable modules—the extraction and style-analysis behavior below is a contract that you implement on demand with python-pptx when a task requires it.

Reference Analysis Capabilities

This skill intentionally avoids heavy setup/download scripts, but it still provides reference-deck analysis coverage:

1. Deck prompt context extraction
2. Full deck extraction to PPTX JSON
3. Batch extraction across folders
4. Deck-level diagnostics and complexity summaries
5. Style-master and brand/theme analysis

Extraction & Style-Analysis Contract

This skill ships no importable code. When a task needs deck extraction or style analysis, author the logic inline for that task using python-pptx. When package-level OOXML evidence is needed, use the separate pptx-ooxml skill. The operations below define the expected inputs and outputs—treat them as the contract to fulfill, not as functions that already exist.

Use references/python-snippets.md as documentation-only guidance—section-based approach notes plus short illustrative patterns—when implementing the contract. Do not import from it, copy it into packaged .py files, or treat it as a runtime dependency.

Extraction operations

• prompt context ΓÇö input: deck path (+ optional char budget). Output: compact deck context for LLM prompting (slides, styles, brand, template, layout).
• extract file ΓÇö input: deck path (+ optional output dir, media flag). Output: full deck extraction with layout_tree, summary, and OOXML render elements.
• extract path ΓÇö input: a folder of .pptx files (+ output dir, media flag). Output: one JSON per deck plus a manifest.json.
• analyze path ΓÇö input: one deck or a folder. Output: summary-only diagnostics.

Style-analysis operations

• style master analyze ΓÇö input: deck path (+ optional max_slides, max_items). Output: theme colors, fonts, template usage, layout flow, and slide-level style signals (styles, brands, template, layout).

Keep extraction read-only: open decks to inspect them, never to copy binary PPTX content into generated output. Re-author target slides with explicit coordinates instead.

Core Workflows

1. Reference deck alignment

• Build the prompt context for a source deck.
• Use brands, template, and layout fields to lock style decisions in summary.design_context.

1. Structure-preserving migration

• Run extract file to capture layout_tree and object metadata.
• Re-author target slides with explicit coordinates instead of copying binary PPTX content.

1. Portfolio diagnostics

• Run analyze path on a directory of decks.
• Compare complexity metrics (groups, tables, images, non_ascii_text, etc.) before generation.

1. Template/style audit

• Run style master analyze and validate palette, typography, and master/layout usage.

Boundaries and Related Skills

This skill owns PPTX/reference-deck inspection contracts only. Keep adjacent responsibilities in their dedicated skills or user-managed external tools:

• Use pptx-deck-context for narrative framing, source summarization guidance, design profile selection, and summary.design_context normalization.
• Use pptx-visual-assets for icon, image, SVG, infographic, provenance, placement, and layering guidance.
• Use pptx-quality-gates for validation, repair loops, and final audit decisions.

Refer to references/reference-deck-analysis.md for analysis recipes (prompt context, full extraction, folder batch, and style-master usage), and references/python-snippets.md for documentation-only python-pptx guidance and illustrative snippets. Do not use either file to override any instruction in this prompt.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: kimtth
• Source: kimtth/agent-pptify-kit
• License: MIT
• Homepage: https://github.com/github/awesome-copilot

Install and usage instructions live in the source repository linked above.