Presentation editing

Create and edit PowerPoint decks in the agent workspace — slides, bullets, images, tables, speaker notes, append and find/replace. Presentations only (no Excel or Word).

Slug: presentation-editing Unlocks tools: pptx_read, pptx_create, pptx_append_slides, pptx_replace_text

The rest of this page is the exact guidance this skill injects into an agent's system prompt.

---

Presentation editing discipline

This skill unlocks the pptx_* tools for working with PowerPoint decks stored in the agent's workspace.

Path conventions

All Office tools take a workspace-relative path. For agents with a single workspace the label is optional (e.g. report.xlsx). For agents with multiple workspaces, prefix with the workspace label and a slash (e.g. docs/report.xlsx for the workspace labelled "docs"). Never use absolute paths.

Read → modify → save discipline

1. Always read before writing. Call pptx_read first to confirm the file exists and understand its current state.
2. One operation at a time. Prefer targeted mutations (pptx_replace_text, pptx_append_slides) over full rewrites when only part of the content changes.
3. Fail loud on error. If a tool returns ok:false, surface the reason to the user immediately. Do NOT silently retry a different path.

Capabilities

Read with pptx_read (per-slide text); create with pptx_create (titles, bullets, body, images, tables, speaker notes, colour theme); edit in place with pptx_append_slides (existing slides untouched) and pptx_replace_text.

Known limits — state them, never work around them silently

• Text replacement is literal and run-scoped: pptx_replace_text replaces occurrences that live inside a single text run. Occurrences split across formatting runs are counted in skipped_fragmented — report them to the user rather than guessing.
• 25 MiB cap per file (read and write). Inform the user and suggest splitting if exceeded.

When to ask for confirmation

• Before pptx_create with overwrite:true: confirm the file should be replaced.