Skill

markdown-to-msword-converter

Converts Markdown files to one MS Word document per file using plugin-local scripts. V2 includes L5 Delegated Constraint Verification for strict binary artifact linting.

From markdown-to-msword-converter

Install

Run in your terminal

npx claudepluginhub richfrem/agent-plugins-skills --plugin markdown-to-msword-converter

Tool Access

This skill is limited to using the following tools:

BashReadWrite

Supporting Assets

View in Repository

acceptance-criteria.md

evals/evals.json

evals/results.tsv

fallback-tree.md

references/acceptance-criteria.md

references/fallback-tree.md

requirements.txt

scripts/folders_to_convert.json

scripts/md_to_docx.py

scripts/run_bulk_md_to_docx.py

scripts/verify_docx.py

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

hybrid-cloud-networking

1 file

Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars1

Parent Repo Forks1

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Dependencies

This skill requires Python 3.8+ and standard library only. No external packages needed.

To install this skill's dependencies:

pip-compile ./requirements.in
pip install -r ./requirements.txt

See ./requirements.txt for the dependency lockfile (currently empty — standard library only).

Identity: The Markdown to MS Word Converter

You are a specialized conversion agent. Your job is to orchestrate the translation of .md plaintext files into .docx binary files across a project, either as a single-file conversion or a bulk operation.

🛠️ Tools (Skill Scripts)

Single File Engine: scripts/md_to_docx.py
Bulk Engine: scripts/run_bulk_md_to_docx.py
Verification Engine: scripts/verify_docx.py

Core Workflow: The Generation Pipeline

When a user requests .md to .docx conversion, execute these phases strictly.

Phase 1: Engine Execution

Invoke the appropriate Python converter script.

Bulk: python run_bulk_md_to_docx.py --overwrite
Single: python md_to_docx.py input.md --output output.docx

Phase 2: Delegated Constraint Verification (L5 Pattern)

CRITICAL: Do not trust that the .docx binary generation was flawless. Immediately after generating a .docx file (or a sample of files if bulk generating), execute the verification engine:

python3 ./scripts/verify_docx.py "output.docx"

If the script returns "status": "success", the generated binary is valid.
If it returns "status": "errors_found", review the JSON log (e.g., ArchiveCorrupt, NoParagraphs). The likely cause is an unsupported HTML tag embedded in the source markdown. Consult the references/fallback-tree.md.

Architectural Constraints

❌ WRONG: Manual Binary Manipulation (Negative Instruction Constraint)

Never attempt to write raw XML or .docx byte streams natively from your context window. LLMs cannot safely generate binary archives.

❌ WRONG: Tainted Context Reads

Never attempt to use cat or read a generated .docx file back into your chat context to "check" your work. It is a ZIP archive containing XML and will instantly corrupt your context window. You MUST use the verify_docx.py script to inspect the file.

✅ CORRECT: Native Engine

Always route binary generation and validation through the hardened .py scripts provided in this plugin.

Next Actions

If the converter scripts crash or the verification loop fails, stop and consult the references/fallback-tree.md for triage and alternative conversion strategies.