I converted the report and saved it as .claude/skills/md-to-docx/sample/report.docx (11 KB). The dependencies installed with only an engine warning: nanoid wants Node 22 or later and this machine has v20.19.0. The conversion ran fine anyway. The description below comes from the document XML, not just the script's success message.
What the document contains
- Title page: "Q3 Platform Review" as the title, "Summary for Engineering" as the subtitle, then "Date: 2026-10-01 | Version: 1.2" and "Audience: Engineering, Product". It is followed by a page break.
- Table of contents: It lists Highlights, Key numbers (indented as a sub-entry) and Plan, then a page break.
- Sections:
- Highlights (heading 2) has a paragraph with bold "18%", italic "0.2%",
status.mdin Consolas with a grey background, and "the dashboard" in blue underline. - Key numbers (heading 3) holds the table.
- Plan (heading 2) has the numbered list "1. Migrate the queue" and "2. Add retries", with "exponential backoff" and "jitter" as indented bullets.
- A Python code block follows, in Consolas on a grey background.
- The document ends with the Chinese paragraph (中文段落：延迟下降 18%。), a horizontal rule and "Done."
- Highlights (heading 2) has a paragraph with bold "18%", italic "0.2%",
- Table: It has 3 columns (Metric, Q2, Q3) and 2 data rows, p95 latency (420 → 344) and Error rate (0.3% → 0.19%). The header row is shaded and repeats across pages, and the rows alternate in colour.
- Image:
diagrams/arch.pngis embedded, centred, with the caption "Architecture".
What did not convert cleanly
- Missing image:
diagrams/nope.pngwas not found, so the document has the placeholder text[Image not found: diagrams/nope.png]. - Mermaid diagram: It was not rendered. The document has the placeholder "[Diagram: See source .md file for interactive Mermaid diagram]".
- Tiny image: The embedded architecture image is only about 0.4 × 0.2 inches (381000 × 190500 EMU). The source PNG is probably a tiny placeholder, so it will look very small in Word.
- Dropped H1: The
# Q3 Platform Review — Summary for Engineeringheading does not appear in the body or the table of contents. Its text is only on the title page. - Link has no URL: "the dashboard" is styled as a link, but there is no hyperlink element in the file, so the
https://example.com/dashURL is lost. - Static table of contents: It is plain text with no page numbers and no links, so it won't update in Word.
- Fake lists: The list markers ("1.", "•") are typed characters with indentation, not real Word lists.
- Code language dropped: The code block keeps its text but not the
pythonlanguage tag, and there is no syntax highlighting. - Chinese font: The Chinese text is set in Calibri, which has no CJK glyphs, so Word will substitute a fallback font. I didn't check how it looks.
How it was tried: the Skill needs npm dependencies, so I had the model run the documented npm install first, then convert a sample Markdown file I built (cover metadata, tables, nested lists, code blocks, a PNG image, one deliberately missing image, a Mermaid code block and a Chinese paragraph). Bash was allowed only for npm install, the conversion command and inspecting the docx internal XML. I also unzipped the docx by hand to check, and the model's description matched. The sample PNG is only a 40x20-pixel placeholder, which is why the text says it is tiny in the document.
What it does
Runs a bundled Node.js script that turns a .md file into a .docx using the docx and marked npm packages, with no Pandoc or LibreOffice needed. It reads YAML front matter (title, date, version, audience) for a title page, builds a table of contents from H1 to H3, styles headings, tables with alternating row colours and code blocks, handles lists, links and rules, and embeds PNG images referenced in the Markdown (paths relative to the file, scaled to about 6 inches wide). Mermaid blocks become a placeholder line.
How it works
- One-time
npm installin the scripts folder. node md-to-docx.mjs input.md [output.docx]; without an output name it writes next to the input name in the current directory.
Good for
Turning documentation, specs and reports written in Markdown into Word files for sharing.
Medium risk: it runs a Node script and needs `npm install` (downloads `docx` and `marked`). It writes the `.docx` to the output path and replaces a file of the same name without asking, so use a new name or keep a backup. Image paths in the Markdown are resolved relative to the input file with no restriction to that folder and no check that the file is a PNG, so converting a Markdown file from an untrusted source can pull other files from disk into the document. The script makes no network requests. Test-run with correct output. Limits: links keep their text but lose the URL, the table of contents is static text with no page numbers or jumps, lists are typed characters, and only PNG is embedded (other image formats are written as PNG and may not display).