Use md-to-docx

Turn a Markdown draft into a Word document (.docx) that someone outside engineering can open, edit and track changes in, with real Heading styles so the navigation pane…

Turn a Markdown draft into a Word document (.docx) that someone outside engineering can open, edit and track changes in, with real Heading styles so the navigation pane and table of contents work, live hyperlinks, numbered and bulleted lists, tables, code blocks, embedded images and optional brand fonts and colours, and a warning for everything that could not be carried over.

Reach for it when the user wants a Markdown file as a Word doc, says "send this as a .docx", "convert to Word", "legal needs it in Word", or "make this editable for the client".

Install it

npx skilldrop-cli install md-to-docx                 # Claude Code, your user folder
npx skilldrop-cli install md-to-docx --project       # Claude Code, this repo
npx skilldrop-cli install md-to-docx --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Converters pack: --pack converters installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Convert README-for-legal.md to a Word document"
• "The client can't open Markdown, can you send the design doc as a .docx?"
• "Make this markdown report editable in Word with our brand fonts"
• "Export these release notes to docx so HR can track changes"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Turn this markdown outline into a PowerPoint deck"
• "Convert the onboarding guide into a single HTML page I can email"
• "Turn this Word file the client sent back into Markdown"

If another skill answers instead, ask for this one by name: "use md-to-docx".

Check what you get

A good result:

• Headings are real Word headings. The navigation pane shows the outline, and Insert Table of Contents works without restyling.
• Every link is clickable and every in-document #anchor link jumps to its heading.
• Nothing is lost silently. Each WARN line is either fixed in the source and gone on rerun, or reported to the user with what it means.
• Facts are untouched. You restructure Markdown (heading levels, footnotes into text) but never change a number, a name or a date in it.
• Images are embedded, not linked, so the file still works when it's emailed.
• The file opens. You checked it with textutil, Quick Look, LibreOffice or Word, not just that the script exited 0.

See a worked example

• q3 support review input
• q3 support review

Use something else when

• Slides; use md-to-pptx
• The other direction, a Word file or PDF back to Markdown; use file-to-markdown
• Tables that need to be sorted, filtered or summed; use md-to-xlsx
• Writing the document itself; draft it first with guide-builder or the skill for that document, then convert

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: brand-kit, file-to-markdown, guide-builder, md-to-xlsx, output-hygiene, release-notes, md-to-pptx

Edit this page on GitHub · View source