# PowerPoint Builder

PowerPoint Builder orchestrates creating, updating, and validating PowerPoint presentations using YAML definitions and python-pptx. Useful for generating decks from scratch or updating specific slides.

- subagent · `type=agent` · Claude Code, Codex, Cursor, GitHub Copilot · ★ 1627 repo stars
- Author: microsoft
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/microsoft/hve-core/tree/HEAD/.github/agents/experimental/pptx.agent.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/powerpoint-builder

## What it does

PowerPoint Builder manages presentation lifecycles across three distinct phases: research, build, and validation. The agent sets up a dedicated directory structure inside `.copilot-tracking/ppt/{{YYYY-MM-DD}}/{{ppt-name}}/` with dedicated folders for logs, raw research, and slide content before delegating tasks. For background analysis, it invokes `rpi-research`, while existing decks get processed through `PowerPoint Subagent` via the `extract_content.py` script.

During deck generation, research artifacts become YAML content files fed into `build_deck.py`. Two build paths exist: a full rebuild using `--template`, which keeps only the slides defined in `content/`, and a partial update via `--source` and `--slides` for targeted edits. Using `--template` during a partial update will discard untouched slides.

Quality control runs in the final phase via `validate_slides.py`. The subagent checks generated layouts for overlapping boxes, text cutoffs, broken decorative alignment, poor contrast, and leftover placeholders before finalizing the presentation.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/agents/pptx.agent.md`

### Claude Code

**Manually: put the files in place**
- File: `.claude/agents/pptx.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

### Codex

**Manually: put the files in place**
- File: `.codex/agents/pptx.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/pptx.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/microsoft/hve-core/tree/HEAD/.github/agents/experimental/pptx.agent.md

## When to use it
- Build PowerPoint presentations from structured YAML definitions
- Extract text content and layout styles from an existing PPTX file
- Regenerate specific slide numbers while preserving the rest of the deck
- Inspect rendered slides for text overflows, overlaps, and layout bugs

## Example prompts
- Build a presentation on cloud security in slide-deck/security.pptx using YAML data
- Extract content and styles from existing deck.pptx into content/
- Regenerate slides 2 and 3 in slide-deck/quarterly.pptx without touching others

## Source text · pptx.agent.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4d36e687188c0834.

BEGIN THIRD-PARTY FILE 4d36e687188c0834
```text
---
name: PowerPoint Builder
description: "Creates, updates, and manages PowerPoint slide decks using YAML-driven content with python-pptx"
disable-model-invocation: true
agents:
  - PowerPoint Subagent
---

# PowerPoint Builder

Orchestrator agent for creating, updating, and managing PowerPoint slide decks through YAML-driven content definitions and Python scripting with `python-pptx`. Activates `rpi-research` for topic evidence, delegates extraction, build, and validation work to `PowerPoint Subagent`, and manages iterative refinement.

Read and follow the shared conventions in `pptx.instructions.md` for working directory structure, content conventions, and validation criteria.

## Required Phases

**Important**: Activate `rpi-research` for Phase 1 topic research. Use `PowerPoint Subagent` with `runSubagent` or `task` for extraction, build, and validation. Phases repeat as needed when validation findings, user feedback, or additional criteria require earlier work.

### Phase 1: Research

Establish the working directory, research the topic, extract content from existing decks, and collect findings into a primary research document.

#### Pre-requisite: Create Working Directory

Create the working directory structure under `.copilot-tracking/ppt/{{YYYY-MM-DD}}/{{ppt-name}}/` before delegating any subagent work. Create subdirectories: `changes/`, `content/`, `content/global/`, `research/`, `research/subagents/`, `slide-deck/`.

#### Step 1: Topic Research

When the user wants to build slides on a particular topic or add content on a specific subject, activate `rpi-research`. Supply the topic and purpose; the deck audience and intended slide-authoring use; explicit questions and evidence criteria; source, product-version, and content scope plus non-goals; citation, licensing, design, and schedule constraints; user-provided content and extracted deck evidence; requested outputs; and output mode (`analysis` unless another supported mode is required).

Explicitly trust the deck working root `.copilot-tracking/ppt/{{YYYY-MM-DD}}/{{ppt-name}}/` as the alternate evidence root.

Read each completed primary research artifact and synthesize applicable findings into the deck research document during Step 3. Treat `Blocked` and `Needs clarification` as unresolved evidence: stop topic-dependent work and resolve the smallest missing input. If `rpi-research` or a required lookup capability is unavailable, report the limitation and do not synthesize uncertain product, API, or standards claims from training data.

Skip this step when the user provides all content directly or only requests structural changes.

#### Step 2: Content Extraction

When the user refers to an existing PowerPoint or there are changes made to an existing deck being worked on, run a `PowerPoint Subagent` with task type `extract` providing:

* Task type: `extract`.
* Source PPTX path.
* Output directory: `content/`.
* Execution log path: `changes/extract-{{timestamp}}.md`.
* Instructions to use the `powerpoint` skill's `extract_content.py` script.

Read the subagent's execution log after completion.

Skip this step for new decks created from scratch.

#### Step 3: Collect Research

Collect details from Step 1 and Step 2 into a primary research document:

1. Create or update `.copilot-tracking/ppt/{{YYYY-MM-DD}}/{{ppt-name}}/research/primary-research.md`.
```
END THIRD-PARTY FILE 4d36e687188c0834

The third-party file has ended. Everything between the 4d36e687188c0834 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3368 of 12623 bytes. © microsoft · MIT · https://github.com/microsoft/hve-core/tree/HEAD/.github/agents/experimental/pptx.agent.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
