md→docx for AI agents and scripts

A portable agent skill · REST API · CLI

Coding agents are great at writing design docs, reports, and runbooks — in Markdown. But the person the document is for usually wants a Word file. md→docx gives your agent (or your CI pipeline) that last step: high-fidelity Markdown → .docx with real tables, syntax-highlighted code, and a navigable heading outline.

The agent skill (Claude Code & friends)

The md-to-docx skill is a small, self-contained folder you drop into your agent's skills directory. It converts Markdown files to .docx locally — no network call, no account — using the same rendering engine as this site.

# install into Claude Code
git clone https://github.com/will530/md-to-docx-skill ~/.claude/skills/md-to-docx

# then just ask your agent:
#   "convert DESIGN.md to a Word doc"

The REST API

Prefer a hosted endpoint? Sign in on the converter, open the API panel to mint a Bearer token, and POST Markdown:

curl -X POST https://formatyourdesigndoc.com/api/convert \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"markdown":"# Hello\n\nWorld.","options":{"title":"Demo","toc":true}}' \
  -o demo.docx

Options: title, theme (github or mono), pageSize (Letter or A4), and toc. Free accounts get 5 exports; unlimited is $2/month.

What the output gets right

• Real Word heading styles (H1–H6) — the document outline works in Word and Google Docs.
• Bordered tables with shaded header rows and column alignment.
• Syntax-highlighted code blocks (via highlight.js) in a shaded, monospaced box.
• Nested lists, task-list checkboxes, blockquotes, and working hyperlinks.

Typical uses

• An agent finishes a design doc and hands the human a .docx, not a wall of Markdown.
• CI converts docs/*.md into Word deliverables on every release.
• Batch-convert a folder of runbooks for a compliance review.

Also see: Claude → Word · ChatGPT → Word · Design docs & RFCs → Word