# Nature Paper2word

Compile an academic Markdown manuscript into a journal- or school-compliant Word...

- Repository: https://github.com/Yuan1z0825/nature-skills (51695 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Yuan1z0825/nature-skills --skill nature-paper2word -g -a claude-code -y`
Codex: `npx skills add Yuan1z0825/nature-skills --skill nature-paper2word -g -a codex -y`
Cursor: `npx skills add Yuan1z0825/nature-skills --skill nature-paper2word -g -a cursor -y`
Gemini CLI: `npx skills add Yuan1z0825/nature-skills --skill nature-paper2word -g -a gemini-cli -y`

## Description

Compile an academic Markdown manuscript into a journal- or school-compliant Word (.docx): declared typography, native OMML equations, three-line tables, cross-references, per-section page numbers, CSL bibliographies (GB/T 7714, APA, Nature, IEEE), and pre/post-export quality gates. 把学术论文的 Markdown 稿件导出为符合期刊或学位论文规范的 Word：摘要、公式编号、三线表、题注、交叉引用、目录域、参考文献。Use when the user wants a submission-ready .docx, 论文转 Word、学位论文排版、期刊投稿排版、prepare submission docx, or a readable copy of a manuscript. Not for PDF, HTML or LaTeX output, and not for slide decks or grant forms.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Markdown → compliant Word

This file is the router. The engine is deterministic: the same manuscript and the same format
requirements always produce a byte-identical `.docx`. Do not substitute a hand-written
python-docx script; run the installed pipeline.

**Before the first export in a session, confirm the engine is available**: `md-to-word --version`
must print a version. This skill ships documentation only; if the command is missing, install it
with `pip install md-to-word-docx`, then run the check again.

**The full vocabulary lives in the manual inside the package**, not here. `md-to-word --contract`
prints its absolute path (Chinese or English, following the manuscript). Everything below is order
of work; every spelling is looked up in the manual.

## 1. Decide the scenario first

| Scenario | What the user says | What to do |
|---|---|---|
| Journal or school compliance | "format it for Nature / my university" | Get a target `.docx` template or a written spec, then build a requirements file. |
| Existing requirements | "use our lab's spec file" | Pass it with `-r`. |
| Baseline export (no explicit spec) | "turn this into a Word file" | Normalize the manuscript to the contract, then export with the built-in preset. The preset is a complete, valid format, not a provisional default. |

State the chosen preset or requirements path in one line, then proceed. Without `-r` the only file
picked up is one named exactly **`format.txt`** beside the manuscript; no other `.txt` is guessed at
(if one is there, the run names it in a reminder). With no `format.txt`, the preset follows the
**manuscript's language**: `zh-academic` for Chinese, `en-nature` for everything else. The run reports
which one it used.

The rest: https://github.com/Yuan1z0825/nature-skills/blob/HEAD/skills/nature-paper2word/SKILL.md