agentleFS
Sign inStart free
sunliangcodesunliangcode/md-to-docx/SKILL.md

md-to-docx

Skill1 starsChanged 24 days agoMITView on GitHub

Converts AI-generated Markdown to professional Word DOCX. Use --preset technical for formal reports; other presets: professional, editorial, academic, business, report. Supports callouts (:::warning/info/note), Mermaid (optional mmdc), reverse, and diff.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. github/awesome-copilot★ 41ksame name
    2. pickle-an/md-to-docx-skill★ 65same name
    3. StevenZhao666/hermes-kits★ 2same name
    4. biomystery/claude-skills★ 1same name
    5. richyuh/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not: run pip install first when using a local skill checkout — use bin/convert or PYTHONPATH.

    line 31
  2. Very specific:

    Run conversion; do not edit source .md.

    line 42
  3. Very specific:

    If markdown contains `mermaid blocks, ensure mmdc on PATH or warn (optional.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

md-to-docx

Turn AI-generated Markdown into professional Word documents. Native Document AST engine (no external converters). MCP and Web Playground available for agent workflows.

Quick start (Cursor skill — no pip install)

Skill root = directory containing this SKILL.md (e.g. ~/.cursor/skills/md-to-docx).

# Formal technical report
"<skill-root>/bin/convert" report.md --preset technical --toc --numbering

# General document
"<skill-root>/bin/convert" report.md --preset professional

# Editorial layout
"<skill-root>/bin/convert" report.md --preset editorial

# Fallback
PYTHONPATH="<skill-root>/scripts" python3 -m md_to_docx report.md --preset technical

Do not run pip install first when using a local skill checkout — use bin/convert or PYTHONPATH.

Agent workflow

  1. Resolve skill-root (parent of bin/convert).
  2. Choose preset by user intent:
    • Formal technical / design doc → --preset technical --toc --numbering
    • Academic paper → --preset academic
    • Editorial / long-form → --preset editorial
    • Business summary → --preset business
    • General document → --preset professional
  3. Run conversion; do not edit source .md.
  4. Report output .docx path to the user.
  5. If markdown contains ```mermaid blocks, ensure mmdc on PATH or warn (optional; CI does not require it).
  6. For MCP clients: see references/mcp.md (pip install .[mcp], md-to-docx mcp).
  7. Reverse (user gives DOCX, wants Markdown source): md-to-docx reverse file.docx -o file.md — see references/roundtrip.md.
  8. Diff two report versions: md-to-docx diff v1.md v2.md --format md.

Behavior

  • Original .md files are never modified
  • Output .docx beside source (foo.md → foo.docx) unless --output-dir
  • Mermaid → PNG under native {stem}-media/ when mmdc is available
  • Callouts: :::warning, :::info, :::note
  • Per-file failures reported; exit non-zero if any failed

Troubleshooting

ErrorFix
No module named md_to_docxUse bin/convert or PYTHONPATH=<skill-root>/scripts
`mmdc` not foundnpm i -g @mermaid-js/mermaid-cli or remove mermaid blocks
Template missingPYTHONPATH=scripts python -m md_to_docx.presets_build

Resources

  • Roundtrip / reverse / diff
  • Plugin API
  • MCP setup
  • Use with ChatGPT
  • Presets
  • Web Playground

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free