| name | documents |
| title | Documents Skill |
| description | Create and convert DOCX documents — contracts, policies, memoranda, letters, term sheets, opinions, press releases, and more. Also converts markdown ↔ DOCX. Use this skill for any Word-document task. For presentations (PPTX) use the presentations skill; for spreadsheets (XLSX) use the spreadsheets skill. |
| author | firelex |
| author_url | https://github.com/firelex/open_teamsuzie/tree/main/packages/skills/templates/documents |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | general |
| language | en |
Documents Skill
Everything Word-document-related lives behind one base URL. Three operations: Draft, Markdown → DOCX, DOCX → Markdown.
Which operation should I use?
You have two ways to produce a new Word document:
-
Draft it yourself in markdown, then use §2 Markdown → DOCX to convert. Good for short or simple documents where you're confident in the structure yourself — quick notes, a letter, a one-page summary, an internal update.
-
Use §1 Draft. This runs the request through a structured drafting pipeline that's particularly well-suited for legal and regulatory documents and other complex documents spanning many pages — contracts, policies, memoranda, engagement letters, term sheets, opinions, press releases, and similar. It produces a properly-templated DOCX in one call.
When you use §1 Draft, include an appropriately detailed description in the instructions field — the drafting pipeline works best with rich context (parties, dates, key terms, tone, length, etc.) rather than a one-line prompt.
Use §3 DOCX → Markdown to read or summarize an existing DOCX the user hands you.
Operation types
- Async (Draft) — you get a
job_id immediately; a webhook fires on completion (30–120s).
- Sync (Markdown → DOCX, DOCX → Markdown) — server returns the final response within a single request/response.
Both kinds share the same download flow: server returns { job_id, download_url, filename }, you fetch the URL, save to workspace, attach the file. Never paste document contents directly into chat — always download to the workspace and attach as a file.
Base URL
{{DOCX_AGENT_URL}}
Authentication
All requests require this header:
X-API-Key: {{AGENT_API_KEY}}
1. Draft a Document (async)
Draft a new DOCX from natural-language instructions. Produces contracts, policies, memoranda, engagement letters, term sheets, opinions, press releases, and similar.
Include a detailed instructions field for optimal results. A rich prompt (parties, dates, key terms, tone, length, intended audience) produces a much better document than a one-line ask. If you only have a short prompt from the user, either ask a follow-up question to enrich it, or use §2 Markdown → DOCX for a simpler path.
