markdown-to-docx

Convert Markdown into branded Word documents using pre-tagged .docx templates.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill markdown-to-docx-eugenelim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-to-docx
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/converters/.apm/skills/markdown-to-docx
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill markdown-to-docx-eugenelim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docxtpl, python-docx, pytest, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns Markdown content into polished Word documents without hand-building .docx files, preserving a designer-made template, branding, and layout while the content is filled automatically.

Core Features & Use Cases

  • Template-based rendering: Fills a pre-tagged Word template from Markdown so cover pages, headers, footers, styles, and logos remain intact.
  • Fill-point inspection: Detects Jinja variables in a template and guides users when a document has no usable fill points.
  • Safe document generation: Supports reports, memos, statements of work, and other branded deliverables, including an explicit unbranded fallback when the user opts out of a template.

Quick Start

Ask the skill to convert your Markdown into a branded Word document using your chosen .docx template and return the generated file path.

Frequently Asked Questions about markdown-to-docx

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

FAQPage Schema
How do I convert Markdown to a Word document while preserving an existing branded template?

To convert Markdown to a branded Word document, this Skill fills pre-tagged .docx templates using docxtpl, preserving the designer's layout, styles, and logos while automatically injecting your content via Jinja placeholders.

How does docxtpl rendering work with Jinja placeholders for document generation?

Docxtpl rendering works by mapping Markdown content to Jinja variables pre-tagged inside a Word template, safely generating files without editing Word XML by hand and applying autoescaping for secure output-path confinement.

Can I generate Word documents from Markdown if my template has no fill points?

Yes, if a template lacks fill points, the Skill performs fill-point inspection to detect Jinja variables and guides users on tagging, or provides an explicit unbranded fallback when you opt out of using a template.

What is the best way to create branded reports from Markdown without editing Word XML?

The best way to create branded reports is using docxtpl-based rendering, which maps Markdown content to a pre-tagged template, keeping headers, footers, and cover pages intact while safely generating the final file.

Does this Markdown to docx conversion work for statements of work and memos?

Yes, this conversion supports template-driven documents like statements of work, memos, and reports, safely filling pre-tagged Word templates from Markdown while preserving the original branding and layout.

Why does my Markdown to Word conversion require a pre-tagged template?

A pre-tagged template is required because the Skill uses docxtpl to map Markdown content to Jinja variables within the document, ensuring the designer's layout and branding remain intact without manual XML editing.