Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Presentations

pptx-from-layouts

Generate and edit consultant-grade PowerPoint decks from markdown outlines using a template's real slide-master layouts (not text overlays). Use when the user wants to create slides/a deck/a presentation from an outline or brief, modify an existing .pptx, turn their own PowerPoint into a reusable template, or check a deck's quality. Triggers: "make a deck", "build a presentation", "slides for…", "use my company template", "fix slide N".

tristan-mcinnis · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add tristan-mcinnis/pptx-from-layouts-skill --skill pptx-from-layouts

About this skill


name: pptx-from-layouts description: >- Generate and edit consultant-grade PowerPoint decks from markdown outlines using a template's real slide-master layouts (not text overlays). Use when the user wants to create slides/a deck/a presentation from an outline or brief, modify an existing .pptx, turn their own PowerPoint into a reusable template, or check a deck's quality. Triggers: "make a deck", "build a presentation", "slides for…", "use my company template", "fix slide N".

PPTX from Layouts — Step 3: Render

Generate consultant-ready PowerPoint presentations from markdown outlines by filling the template's actual slide-master layouts. Core thesis: use the template's layouts and placeholders — never overlay text boxes on slides.

The 3-step pipeline

This skill is Step 3 of a three-skill pipeline. Each step is its own skill:

  STEP 1 — PROFILE          STEP 2 — AUTHOR           STEP 3 — RENDER  ◀ you are here
  pptx-profile              pptx-author               pptx-from-layouts
  ───────────────           ───────────────           ─────────────────
  your-template.pptx        slides.md (+ [HINT:])     slides.md + config
        │                         │                         │
        ▼                         ▼                         ▼
   catalog.py  ──catalog.md──▶  write & lint  ──slides──▶  generate.py ─▶ deck.pptx
        └────────────────── config.json ───────────────────▲   (validated)
  "what layouts do I        "write slides that        "fill the template's
   have?"                    name real layouts"        actual placeholders"
  • Step 1 — pptx-profile: catalog.py turns a .pptx into a layout catalog (the menu of [HINT:] names) + a render config.json. One-time per template.
  • Step 2 — pptx-author: write slides.md with [HINT: layout_name] per slide, then lint_hints.py validates the hints against the catalog.
  • Step 3 — this skill: generate.py fills the named layouts and validates.

You can also start here directly with the bundled Inner Chapter template (no Step 1 needed) — it's the default and the running example throughout this doc.

[HINT:] — author against real layouts

A slide can name the exact template layout it should render on:

# Slide 2: Three outcomes the research must achieve

[HINT: column-3-centered-a]

[Column 1: Level-set] …

[HINT:] resolves against the active template config (from Step 1), so it works for any profiled template — not just Inner Chapter. It's equivalent to the **Layout:** marker, and takes precedence over **Visual:**. Use [HINT:] when you know the layout (precise); use **Visual:** when you want the engine to auto-pick one for a semantic intent (e.g. process-4-phase). Mismatched hints fall back to auto-detection with a warning — so lint in Step 2 first.

Dependencies (check first)

Requires Python 3.10+, python-pptx, and pydantic:

pip install python-pptx pydantic     # or: pip install -r requirements.txt

If you hit ModuleNotFoundError: No module named 'pptx' or 'pydantic', this is why. The entry-point scripts set their own PYTHONPATH; run them directly with python.

Decision: which path am I on?

The user wants…Do this
A deck from a brief / notes / source doc (no outline yet)Delegate to pptx-outline-architect, then generate
A deck and they already wrote an outlinegenerate.py → validate
To use their own PowerPoint as the templateDelegate to pptx-template-onboarder (one-time setup)
Small text fixes / reorder on an existing deck (<30% slides)edit.py (inventory → replace / reorder)
Layout changes, added/removed slides, or >30% churnRegenerate via generate.py — never edit
To know if a deck is goodDelegate to pptx-deck-qa or run validate.py

Mandatory generation workflow (do not skip steps)

  1. Pick or confirm the template. First time with a custom template? Onboard it once (see Bring your own template below). Otherwise the bundled Inner Chapter template is the default.
  2. Produce an outline with a **Visual: <type>** declaration on EVERY content slide. Choose visual types with the decision order below — do not default everything to bullets.
  3. Generate:
    python scripts/generate.py outline.md -o deck.pptx --validate
    
    (Add --template <t.pptx> --config <c.json> for a custom template.)
  4. Validate and read the report. A deck is not done until validation is clean of errors and text overflow. If it isn't, fix and re-run.
  5. Report the score and the output path to the user.

Definition of done (self-check before claiming success)

  • Every content slide had an explicit **Visual:** declaration.
  • generate.py exited successfully and the .pptx exists.
  • validate.py reports zero errors and no text overflow.
  • No anti-pattern below was used (hero-statement for lists, tables for process flows, bullets for comparisons, …).
  • You reported the validation score and file path, not just "done".

If any box is unchecked, the task is not finished — fix it or say explicitly what blocked you.

Subagents

Canonical definitions in agents/; install to ~/.claude/agents/ to use them.

SubagentUse it to
pptx-outline-architectTurn raw material into a generation-ready outline.md with correct visual types
pptx-template-onboarderOnboard a user's .pptx as a reusable, on-brand template (one-time)
pptx-deck-qaValidate a deck and apply a surgical fix or recommend regeneration

They chain as architect → generate.py → QA; for your own template, onboarder runs once up front. (Full write-up: docs/workflows.md in the repo.)

Quick Start

# Generate from outline (bundled Inner Chapter template, with validatio
Read the complete source ↗