Z Md To Word logo

Z Md To Word

Community
tjxj
z-md-to-word

Convert local Markdown files into Word documents. Use this skill whenever the user provides a .md path and says 转成doc, 转成 Word, Markdown 转 Word, Markdown转doc, md 转 doc, md转docx, 导出 Word, 生成 doc, 生成 docx, or asks for a Word version of an article. This skill should produce a .docx by default, also produce a legacy .doc when useful, embed valid images, skip empty upload placeholders, keep Markdown lists readable, write outputs under output/doc, and verify the generated files before reporting.

Overview

Publishertjxj
Repositoryz-skills
Skill namez-md-to-word
Stars
548
Forks
102
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by tjxj on GitHub. Read the source before you install it.

Installation

Install the Z Md To Word AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/tjxj/z-skills/tree/main/z-md-to-word
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tjxj/z-skills.git /tmp/z-skills
mkdir -p .claude/skills
cp -r /tmp/z-skills/z-md-to-word .claude/skills/z-md-to-word
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Z Md To Word in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Z Md To Word on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Z Md To Word is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Markdown to Word

Use This For

  • A local .md article needs to become a Word file.
  • The user says "转成doc", "转成 Word", "md 转 doc", "Markdown 转 Word", "导出 Word", or similar.
  • The input is usually an Obsidian or WeChat article with YAML frontmatter and remote images.

Completion Standard

Finish only after all of these are true:

  • The .docx file exists under output/doc/.
  • If the user asked for .doc, a legacy .doc file also exists.
  • The document can be opened or rendered by LibreOffice.
  • The extracted text includes representative beginning, middle, and ending content.
  • Valid images are embedded; empty upload placeholders like ![]( ) or ![Uploading file...]() are skipped.
  • Markdown lists are readable as lists, even when the source omitted a blank line before -.

Preferred Command

From the workspace root:

bash
python3 .agent/skills/z-md-to-word/scripts/md_to_word.py "/absolute/path/to/article.md"

The script writes outputs to:

text
output/doc/<markdown-stem>.docx
output/doc/<markdown-stem>.doc

Use --no-doc only when the user explicitly wants .docx only.

Workflow

  1. Confirm the Markdown file exists.
  2. Run the bundled script.
  3. Read the JSON summary printed by the script.
  4. If rendered_docx or rendered_doc is false, fix the cause and rerun.
  5. If layout quality matters, rerun with --keep-render, open the generated contact sheet, and inspect the pages.
  6. Report only the final file paths and the verification result.

Details Captured By The Script

  • Uses Pandoc with markdown+yaml_metadata_block+lists_without_preceding_blankline.
  • Preserves frontmatter title, author, and date as Word document metadata/title block.
  • Removes empty image nodes before conversion, so upload placeholders do not appear in the final document.
  • Embeds valid local or remote images into the .docx.
  • Converts .docx to .doc through LibreOffice when available.
  • Validates the .docx ZIP structure.
  • Extracts plain text for a content sanity check.
  • Renders Word files to PDF when LibreOffice is available.

Fallback

If the script cannot run, use this direct conversion pattern:

bash
pandoc "input.md" \
  --from markdown+yaml_metadata_block+lists_without_preceding_blankline \
  --to docx \
  --standalone \
  --resource-path="/path/to/input-dir:/workspace/root" \
  --lua-filter="/tmp/remove-empty-images.lua" \
  --output "output/doc/name.docx"

/tmp/remove-empty-images.lua:

lua
function Image(img)
  if img.src == "" then return {} end
end

Then render and inspect:

bash
soffice -env:UserInstallation=file:///tmp/lo_profile_$$ \
  --headless --convert-to pdf --outdir tmp/docs/check "output/doc/name.docx"

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Z Md To Word AI skill do?

Convert local Markdown files into Word documents. Use this skill whenever the user provides a .md path and says 转成doc, 转成 Word, Markdown 转 Word, Markdown转doc, md 转 doc, md转docx, 导出 Word, 生成 doc, 生成 docx, or asks for a Word version of an article. This skill should produce a .docx by default, also produce a legacy .doc when useful, embed valid images, skip empty upload placeholders, keep Markdown lists readable, write outputs under output/doc, and verify the generated files before reporting.

Why use Z Md To Word on TypingMind?

Because you install it once and use it with any model. Z Md To Word is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Z Md To Word in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tjxj/z-skills/tree/main/z-md-to-word. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Z Md To Word?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Z Md To Word?

As many as you like. As long as a model supports skills, you can use Z Md To Word with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Z Md To Word AI skill free?

It is published on GitHub by tjxj. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇