Office Documents

Office document handling comes from four independent plugins, each with its own constraints and failure modes:

Word documents

profy-docx — docx-js generation, unpack-and-edit XML, cross-run text replacement, tracked changes

Excel spreadsheets

profy-xlsx — formulas over hardcoded values, zero formula errors, financial model conventions

PDF documents

profy-pdf — WeasyPrint creation (mandatory) plus pypdf/qpdf manipulation, including the kami typesetting engine

Presentations

profy-pptx — native .pptx (SVG → DrawingML) and HTML Deck, two mutually exclusive pipelines

What the four have in common

Dimension	Value
Activation	All `user_selectable: false` — automatically available, invisible in the plugin panel
Contract	All declare only `skills`, with no tools
Execution	The expert runs scripts in the sandbox via `bash` / `skill(execute)`, governed by the skill document

The “no tools” property deserves comment. These four plugins do not expose button-like interfaces such as “generate a Word document”. They supply methods and scripts. The upside is that the capability ceiling equals whatever can run in the sandbox, rather than being fixed by a tool signature — which matters for document work, where requirements are unusually open-ended.

Choosing between them

What you want	Go to
An editable formal document with a TOC and page numbers	Word
A live spreadsheet or financial model that reacts to source data	Excel
A beautifully typeset fixed-layout deliverable (resume, white paper, one-pager)	PDF (kami)
Extract / merge / split / fill an existing PDF	PDF (manipulation path)
Slides someone will keep editing in PowerPoint	Presentations (native PPTX)
A visually striking talk shown straight from a browser	Presentations (HTML Deck)

Three wrong turns worth naming

Wanted a PDF, built an HTML Deck. HTML Decks cannot export to PDF (Tailwind and WebGL do not render). If PDF is the requirement, take the kami route from the start.
Wanted an editable deck, wrote a custom converter. Custom scripts produce image-only slides with broken CJK text. The svg_to_pptx.py pipeline is the only supported route.
Wanted a live model, got a snapshot of numbers. Every calculation in Excel must stay a formula; hardcoded results become silently wrong the moment one input changes.

All three share a shape: the wrong path is easier, succeeds without error, and produces something that looks right until someone tries to use it.

One sentence that picks the right path

The deciding factor isn’t the file extension — it’s who picks the deliverable up next and what they do with it. Put that in the request and the Expert can’t take the wrong pipeline:

✓ A 12-page product white paper as PDF, ready to send to clients,
  beautifully typeset, nobody edits it afterwards
  → PDF / kami typesetting

✓ A quarterly financial model in Excel where margin recalculates
  when I change unit price or quantity
  → Excel, everything stays a formula

✓ A 15-slide fundraising deck I'll keep editing in PowerPoint
  → Native PPTX (svg_to_pptx.py)

✓ A launch deck shown straight from the browser, with animation and impact
  → HTML Deck (note: it can't be exported to PDF later)

✗ Make me a deck, and ideally also a PDF version
  → The two pipelines are mutually exclusive; you'll get the one you didn't
    want. Name the primary deliverable first.

Shared constraints

Large documents — PDFs over 100 pages, DOCX files with many images — take a long time to process. Split them before uploading when practical.

Constraint	Value	Note
Per-file limit (documents)	512 MB	Hardcoded by type, independent of plan
Attachments per message	10	Split across messages beyond that
Default sandbox command timeout	120 seconds	Long jobs need an explicit larger timeout
Recommended pages per pass	Under 100	Split first, or the whole turn stalls
Dependency installs	0	Preinstalled in the image; nothing installed at runtime

The sandbox image has all dependencies preinstalled. Do not run pip install at runtime; an import failure is an image bug.
Operations involving LibreOffice (xlsx formula recalculation, doc→docx conversion, accepting tracked changes) depend on LibreOffice being present in the sandbox.
When modifying an existing file, its established conventions outrank any default guideline — you do not know what downstream depends on them.

Failures and fixes

Per-format failure modes live on each plugin’s page; these are the ones shared across all four:

Symptom	Cause	Fix
None of the four appear in the plugin panel	They are `user_selectable: false` — automatically available, never listed	No ticking needed; just state the requirement
”There’s no tool for generating Word”	These plugins declare skills only and expose no tools	Have it run the scripts in the sandbox as the skill documents
A script fails on import	Image dependency bug, not a missing package	Do not let it `pip install`; report it
A command is cut off mid-run	Sandbox commands time out after 120 seconds by default	Have the Expert split steps or raise the timeout explicitly
xlsx prompts to recalculate, or formulas show 0	Formula recalculation depends on LibreOffice in the sandbox	Have it recalculate through LibreOffice before exporting
Edited an existing file and broke a downstream template	Its established conventions were overwritten	When editing existing files, follow that file’s conventions over any default
An HTML Deck won’t export to PDF	The pipelines are mutually exclusive (Tailwind and WebGL don’t print)	If PDF is required, rebuild via kami from the start

Billing

Credit consumption for document work comes from model token usage in the conversation. Generating and downloading the files themselves carries no additional charge.

Verified 2026-08-11. Sources: services/agent-runtime/src/plugins/builtin/{docx,xlsx,pdf,pptx}/plugin.json and their respective skills/ directories.

Get Started

Core Concepts

Guides

Platform & Account

Deep Dive

Office Documents

Office Documents

Word documents

Excel spreadsheets

PDF documents

Presentations

What the four have in common

Choosing between them

Three wrong turns worth naming

One sentence that picks the right path

Shared constraints

Failures and fixes

Billing

​Office Documents

Word documents

Excel spreadsheets

PDF documents

Presentations

​What the four have in common

​Choosing between them

​Three wrong turns worth naming

​One sentence that picks the right path

​Shared constraints

​Failures and fixes

​Billing

Office Documents

What the four have in common

Choosing between them

Three wrong turns worth naming

One sentence that picks the right path

Shared constraints

Failures and fixes

Billing