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.
试用方式:Skill 需要 npm 依赖,我让模型先执行文档里的 npm install,再转换我构造的示例 Markdown(含封面信息、表格、嵌套列表、代码块、PNG 图片、一个故意缺失的图片、Mermaid 代码块、中文段落);Bash 只放行 npm install、转换命令和查看 docx 内部 XML 这三条。我另外手动解压 docx 核对,模型的描述与实际一致。示例中的 PNG 只是 40×20 像素的占位图,所以文中说它在文档里很小。
它做什么
运行随包的 Node.js 脚本,借助 docx 和 marked 两个 npm 包把 .md 文件转成 .docx,不需要 Pandoc 或 LibreOffice。它读取 YAML 前置信息(标题、日期、版本、读者)生成封面,根据 H1 到 H3 标题生成目录,给标题、隔行变色的表格和代码块设置样式,处理列表、链接和分隔线,并嵌入 Markdown 里引用的 PNG 图片(路径相对于该文件,缩放到约 6 英寸宽)。Mermaid 代码块会变成一行占位文字。
工作方式
- 在 scripts 文件夹里一次性执行
npm install。 - 执行
node md-to-docx.mjs input.md [output.docx];不写输出名时,会在当前目录按输入文件名生成。
适合什么场景
把用 Markdown 写的文档、规格说明和报告转成 Word 文件用于分享。
中风险:它运行一个 Node 脚本,需要 `npm install`(下载 `docx` 和 `marked`)。它把 `.docx` 写到输出路径,同名文件会被直接替换而不询问,请换一个新名字或先备份。Markdown 里的图片路径是相对输入文件解析的,没有限制在该文件夹内,也不检查是不是 PNG,所以转换来路不明的 Markdown 可能把磁盘上其他文件嵌进文档。脚本不发起网络请求。已试用,转换结果正确。限制:链接只保留文字、不保留网址;目录是静态文字,没有页码和跳转;列表是用字符模拟的;只嵌入 PNG,其他图片格式会被当作 PNG 写入,可能无法显示。