What is spec-kit-export-docx?

A Markdown-to-DOCX export procedure for turning repository documentation into Word files. It supports selected documentation scopes and formatting options.

Use it to export the specification, kit documentation, or all documentation, with options for history, title, table of contents, and page breaks.

It avoids manually copying Markdown into Word when sharing project documents with people who require a DOCX file.

How lksnext-ai-lab/spec-kit-template configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to lksnext-ai-lab/spec-kit-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lksnext-ai-lab/spec-kit-template/main/.github/skills/spec-kit-export-docx/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-template

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx/github.svg)](https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx)

Your own site

<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/spec-kit-export-docx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01169
Opus 5.5	$0.00000	$0.00468
Sonnet 5.5	$0.00000	$0.00234
Haiku 4.5	$0.00000	$0.00117

Measured 2mo ago against content hash 4eae116ae5f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-kit-export-docx scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/spec-kit-export-docx/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SKILL: export-docx (Markdown → DOCX)

Propósito

Exportar documentación Markdown del repo a DOCX usando el script:

python tools/export_docx.py

Permite elegir alcance (scope) y opciones de formato, sin modificar docs/**.

Cuándo usarlo

Compartir documentación con terceros en formato Word.
Entregables fuera del repositorio (auditorías, stakeholders, etc.).
Revisiones donde DOCX sea requisito.

Alcances soportados (scope)

Scopes soportados por el script (no inventar):

spec → docs/spec/** (excluye docs/spec/history/** por defecto)
kit → docs/kit/**
all → docs/** (excluye docs/spec/history/** por defecto)

Nota: existe --include-history para incluir docs/spec/history/** solo en spec o all.

Entrada que debes pedir al usuario

scope: spec | kit | all (default recomendado: spec)
output: ruta del .docx (default recomendado: exports/spec.docx)
title (opcional)
toc: sí/no (default recomendado: no)
page breaks: sí/no
- Por defecto el script inserta saltos de página entre secciones.
- Para desactivarlo: --no-page-break
include-history: sí/no (solo útil en spec o all; default: no)

Requisitos previos (siempre)

Estar en la raíz del repo (debe existir docs/)
Pandoc disponible en PATH:
- comprobar: pandoc --version
Si existe mkdocs.yml con nav: (para respetar orden):
- instalar PyYAML: python -m pip install pyyaml

Reglas duras

NO modificar docs/** (solo lectura).
Output recomendado en exports/.
No inventar flags: el script soporta exactamente:
- --scope {spec,kit,all}
- --output <ruta.docx>
- --title "<título>"
- --toc
- --no-page-break
- --include-history

Orden de documentos (cómo funciona)

Si existe mkdocs.yml con nav:, el script usa ese orden (requiere PyYAML).
Si no existe mkdocs.yml o no hay nav, usa un orden fallback por convención.

Read the full file on GitHub · 181 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 181 lines · 0 tokens per session scan A 4eae116ae5f0

Subscribe to this mod's changes

spec-kit-export-docx is a skill published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,169 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Documents Writing and docs spec-kit

spec-kit-export-docx next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-kit-export-docxlksnext-ai-lab/spec-kit-template	Skill	5	8mo ago	Apache-2.0	A	0	Claude Code, Codex
orbit-notionnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	117	Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	2d ago	Apache-2.0	A	123	Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	48	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	68	Claude Code
ppt-reviewOrkas-AI/Orkas	Skill	9.0k	yesterday	MIT	A	2	Claude Code, Codex
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex

spec-kit-template: Skill for Claude Code