doc-to-doc-converter

Convert Markdown files in docs/ to DOCX using pandoc.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Xunzi229/skills --skill doc-to-doc-converter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-to-doc-converter
Source: https://github.com/Xunzi229/skills/tree/main/doc-to-doc-converter
Command: npx skills add https://github.com/Xunzi229/skills --skill doc-to-doc-converter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandoc, and includes scripts (resource) components.

What problem does it solve?

Automates the repetitive task of converting Markdown documentation into a doc format so documentation stays synchronized without manual Pandoc invocations.

Core Features & Use Cases

  • Directory Watch & Triggering: Targets Markdown files under the docs/ directory and runs conversions when files are added or modified or when a user requests a conversion.
  • Deterministic Conversion Script: Uses a repository script to run Pandoc and produce .docx outputs, emitting a single-line success message per file.
  • Use Case: Keep a project's human-readable documentation in sync by converting updated docs/*.md files to .docx for distribution or offline review.

Quick Start

Convert the updated Markdown files in the docs directory to .docx using the doc-to-doc-converter skill.

Frequently Asked Questions about doc-to-doc-converter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically convert Markdown to DOCX when files change?

Automatically converting Markdown to DOCX requires watching the docs/ directory for file modifications and triggering a pandoc script to generate .docx outputs, keeping documentation synchronized without manual invocations.

Do I need pandoc installed to convert Markdown files to DOCX?

Yes, you need pandoc installed on your system to convert Markdown files to DOCX, as the conversion script invokes pandoc directly from the repository root to process the documentation files.

What is the best way to keep project documentation in sync as DOCX files?

Keeping project documentation in sync as DOCX files is best handled by automating pandoc conversions targeting the docs/ directory, ensuring updated Markdown files are transformed into .docx for distribution or offline review.

Does the Markdown to DOCX conversion script work outside the docs directory?

No, the Markdown to DOCX conversion script specifically targets Markdown files located within the docs/ directory and will not automatically process files added or modified outside of that path.

How does the conversion script confirm a successful Markdown to DOCX conversion?

The conversion script confirms a successful Markdown to DOCX conversion by emitting a single-line success message for each processed file, verifying that the pandoc execution completed properly.