docx · diff

v1.1 to v1.1

1 added, 2 removed. Audit A to A.

---

name: docx

description: Create editable Word documents (.docx) on demand — reports, proposals, concepts, letters, minutes, specifications, manuals, contract drafts — with real Word headings, lists, tables, callouts, a cover page and a table of contents, in the company's document template. Use whenever the user asks to create, generate or export a Word document, a .docx file, or an editable document they want to keep working on. Do NOT activate just to read, summarize or answer questions about an uploaded .docx file (its extracted text is already in the conversation context).

metadata:

author: IntraFind

version: '1.1'

allowed-tools: create_docx

---

# Creating Word documents

You create Word documents with the `create_docx` tool. You write the content as Markdown; the server turns it into a real, editable Word document: Markdown headings become Word headings (Heading 1, Heading 2, …), lists become Word lists, tables become Word tables. The user gets a download card in the chat.

## Choose the format

- **Word (`create_docx`)** when the user wants to keep editing the document, send it for review with track changes, or paste it into their own documents.

- **PDF (`create_pdf`, if the `pdf` skill is available)** when the user wants a finished, printable document with a fixed layout, SVG charts, QR codes or a multi-column layout.

- **PowerPoint (`create_pptx`, `pptx` skill)** when the user wants a slide deck or presentation.

- **Excel (`create_xlsx`, `xlsx` skill)** when the user wants a spreadsheet, workbook or multi-sheet data table with formulas.

- **Interactive HTML pages or standalone SVGs (`create_web_artifact`, `web-artifacts` skill)** when the user wants an interactive dashboard, calculator, simulator or a standalone `.svg`. These go through `create_web_artifact`, not `create_file`: it adds the brand tokens, checks the page and shows a sandboxed preview.

- **Code, CSV, calendar invites or archives (`create_file` / `create_zip`, `files` skill)** when the user wants source code, a data file, a calendar invite (`.ics`), or a ZIP archive.

- If the user just says "a document", ask only if it matters; otherwise prefer Word for drafts and PDF for final hand-outs.

## How uploaded Word files work

- **Reading uploaded `.docx` files:** When the user uploads a Word document in chat, the platform has **already extracted its text and tables into `<content type="document">` in your prompt context**. Read, summarize or answer questions directly from that context.

- **Revising an uploaded `.docx` file:** `create_docx` always generates a fresh Word document; it cannot insert Track Changes (`<w:ins>` / `<w:del>`) or comments into the original file in place. When the user asks to revise or rewrite an uploaded Word document, generate a new `.docx` from the extracted text in your context.

- - **Using an uploaded `.docx` as a template:** when its `<content>` tag says `can_use_as_template="true"`, pass its `id` as `templateFileId`. The new document then gets the upload's styles, headers/footers and page setup. `templateMode` decides what happens to the upload's own body text: `styles_only` (the default when the file has no `{{content}}` marker) drops it, `fill_placeholders` fills `{{title}}`, `{{date}}`, … and inserts your content at `{{content}}`, `append` adds your content after it. Do not claim to have used the user's template unless you passed `templateFileId`.

## The company template

If the app uses a **document template**, the server applies it automatically: the company's Word template (styles, header, footer, logo, page setup, and `{{title}}` / `{{subtitle}}` / `{{author}}` / `{{date}}` / `{{company}}` / `{{content}}` placeholders) or its brand colours, fonts and logo. Then:

- Do not try to imitate the corporate design yourself, and do not set `primaryColor`, `accentColor` or `font`.

- Do not repeat the company name, logo text or a confidentiality line in the content: the header and footer have them.

- If `create_docx` offers a `template` parameter, use `default` unless the user asks for a specific template.

## Workflow

1. **Plan the document.** Audience, purpose, sections, key facts. Ask only when essential facts are missing.

2. **Write the content as Markdown** in `markdown`. Start with the first section — the title is printed already; do not repeat it as a `#` heading.

3. **Call `create_docx`** with a descriptive `filename`, the `title`, the `language` of the content and the `markdown`. Add `subtitle`, `author`, `date`, `showTitle: false` (for letters), `coverPage` (formal documents of more than about three pages) and `toc` (four or more sections) as needed.

4. **Answer briefly.** Name the file and summarise it in one or two sentences. Do not paste the document into the chat and do not add a link: the download card is already there.

If `create_docx` returns `warnings`, read them. They name content that was skipped (for example an unsupported image). Fix what matters and create the file again.

## Writing for Word

- **Use heading levels consistently**: `#` for main sections, `##` and `###` below them. Never skip levels. The table of contents is built from levels 1–3.

- **Keep paragraphs short**; use bullet lists for enumerations and numbered lists for steps.

- **Tables**: GFM tables, at most 6–7 columns in portrait (use `orientation: "landscape"` for wider ones). Right-align numbers (`|---:|`), give units in the header.

- **Callouts**: GitHub alerts become shaded boxes:

```markdown

> [!IMPORTANT]

> The offer is valid until **31 March**.

```

Kinds: `NOTE`, `TIP`, `IMPORTANT`, `WARNING`, `CAUTION`. One or two per page at most.

- **Quotes**: `> text` becomes a Word quote.

- **Code** in fenced blocks.

- **Page breaks**: a line with only `\pagebreak`, before major parts such as an appendix.

- **Images** only as `data:image/png;base64,…` or `data:image/jpeg;base64,…`; you cannot fetch images from URLs.

- **Sub- and superscript**: `H<sub>2</sub>O`, `m<sup>2</sup>`.

- **Not supported**: Mermaid, LaTeX math, HTML layout, footnotes, comments and tracked changes. Charts are not drawn in Word documents; give the numbers as a table, or create a PDF or presentation for charts.

- - **Letters**: set `showTitle: false` and `pageNumbers: false`, and put the recipient block, date line and bold subject line as normal paragraphs at the top of `markdown`, followed by the salutation and body.

+ - **Letters**: set `showTitle: false` and `pageNumbers: false`, and put the recipient block, date line and bold subject line as normal paragraphs at the top of `markdown`, followed by the salutation and body. A document template that sets `document.pageNumbers` wins over `pageNumbers: false`, so with such a template a letter can still show page numbers.

## Quality checklist

- Title, `language` and file name fit the content.

- No empty sections, placeholder text or `TODO`s unless the user asked for a template to fill in.

- Numbers, dates and currency formats are consistent.

- For a revision, create a new file: documents are never edited in place.