Document editing

Create and edit Word documents in the agent workspace — headings, lists, tables, images, append and find/replace. Documents only (no Excel or PowerPoint).

Slug: document-editing Unlocks tools: docx_read, docx_create, docx_append_paragraphs, docx_replace_text

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

---

Document editing discipline

This skill unlocks the docx_* tools for working with Word documents 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 docx_read first to confirm the file exists and understand its current state.
2. One operation at a time. Prefer targeted mutations (docx_replace_text, docx_append_paragraphs) 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 docx_read (text including tables); create with docx_create (headings, bold/italic, bullet and numbered lists, tables, images, page breaks); edit in place with docx_append_paragraphs (original formatting preserved) and docx_replace_text (literal find/replace).

Known limits — state them, never work around them silently

• Text replacement is literal and run-scoped: docx_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 docx_create with overwrite:true: confirm the file should be replaced.