pandoc-extensions

Select Pandoc Markdown extensions and command profiles for DOCX conversion workflows.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/nimdvir/dima-publishing --skill pandoc-extensions-nimdvir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pandoc-extensions
Source: https://github.com/nimdvir/dima-publishing/tree/main/.agents/skills/pandoc-extensions
Command: npx skills add https://github.com/nimdvir/dima-publishing --skill pandoc-extensions-nimdvir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right Pandoc Markdown extensions and command flags is confusing, and the wrong combination causes rendering gaps when converting Markdown to DOCX, HTML, or EPUB. This Skill provides decision rules, a full extension catalog, and copy-paste command profiles so conversions produce the expected output. ## Core Features & Use Cases - Extension Selection Guidance: A complete catalog of Pandoc extensions (footnotes, citations, fenced_divs, alerts, mark, and more) with when-to-use notes for each. - Command Profiles: Ready-to-use Pandoc command presets for portable DOCX output, GFM alert parsing, and CommonMark-focused conversion. - DOCX Fallback Patterns: Reliable workarounds for features that do not render in DOCX, such as alerts as styled blockquotes and columns as two-column tables. - Use Case: You are converting a GitHub-flavored Markdown manuscript to DOCX for a publisher and the alert blocks render as plain text. Use this Skill to pick the gfm+alerts+mark profile and apply the blockquote fallback pattern. ## Quick Start Ask which Pandoc extensions and command profile to use for converting a GFM manuscript with alerts and footnotes into a DOCX file.

Frequently Asked Questions about pandoc-extensions

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

FAQPage Schema
How do I convert Markdown to DOCX with Pandoc?▼

Use a portable extension profile such as pandoc input.md -f markdown+fenced_divs+native_divs+header_attributes+link_attributes+footnotes+citations+mark -t docx -o output.docx. This combination covers the most common manuscript features while keeping DOCX output predictable.

Which Pandoc extensions should I enable for DOCX output?▼

Start with fenced_divs, native_divs, header_attributes, link_attributes, footnotes, citations, and mark on the markdown reader. For GitHub-style alerts use gfm+alerts+mark, and for strict CommonMark behavior use commonmark_x+attributes+mark.

What is the difference between markdown, gfm, and commonmark_x in Pandoc?▼

The markdown reader supports the broadest extension set and suits DOCX publishing. gfm matches GitHub rendering including alerts and task lists, while commonmark_x follows the CommonMark spec with optional extras like attributes for stricter parsing.

Why do GitHub alerts not render in Pandoc DOCX output?▼

GitHub alert markers like [!NOTE] may remain literal text in DOCX depending on the reader profile. The reliable fallback is to write alerts as blockquotes with bold labels such as **Note:**, which render consistently in DOCX.

Can Pandoc create two-column layouts in DOCX?▼

Native Markdown column syntax is not guaranteed to produce side-by-side layout in DOCX. The dependable pattern is a two-column Markdown table, with left content in one cell and right content in the other.

Does CSS styling apply to Pandoc DOCX output?▼

No, CSS styles only affect HTML output. DOCX styling comes from the reference document template, so use a reference-doc with defined styles rather than relying on CSS or inline HTML styling.