菜单
Convert a Markdown file to DOCX (Word). Use when the user asks to convert .md to .docx, generate a Word document from Markdown, or export Markdown notes to Word.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
1C metadata management — create, edit, validate, and remove configuration objects (catalogs, documents, registers, enums), managed forms, data composition schemas (SKD), spreadsheet layouts (MXL), roles, external processors (EPF/ERF), extensions (CFE), configurations (CF), databases, subsystems, command interfaces, templates. Use when working with 1C metadata structure.
Catalog of MCP servers for 1C development — search, code navigation, metadata, code review, docs, ITS, templates. Use whenever a 1C task requires calling tools from any 1c-*-mcp / 1C-*-mcp server. Each server has its own detail file under `docs/` — load it when you are about to call tools from that server, and only if the server is actually available in the current session.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
| name | md-to-docx |
| description | Convert a Markdown file to DOCX (Word). Use when the user asks to convert .md to .docx, generate a Word document from Markdown, or export Markdown notes to Word. |
Converts a Markdown file to a Word document (.docx) preserving headings, tables, lists, code blocks, links and inline images.
/md-to-docx <input.md> [output.docx]
| Parameter | Required | Description |
|---|---|---|
input.md | yes | Path to the source Markdown file |
output.docx | no | Path to the output file (default: alongside source, .md → .docx) |
If the path is not provided — ask the user.
docx — install globally: npm install -g docx<skill-dir> below is the directory of this skill: content/skills/md-to-docx/ in the 1c-rules source repo, or <tool>/skills/md-to-docx/ after installation (e.g. .cursor/skills/md-to-docx/, .claude/skills/md-to-docx/).
PowerShell (Windows, default for this project):
$env:NODE_PATH = (npm root -g)
node <skill-dir>/scripts/md_to_docx.js "<input.md>" "[output.docx]"
Bash (macOS / Linux):
NODE_MODULES=$(npm root -g)
NODE_PATH="$NODE_MODULES" node <skill-dir>/scripts/md_to_docx.js "<input.md>" "[output.docx]"
code, links) — resolved relative to the source MD folder---)If an image is not found — a red text placeholder is inserted.
Created: output.docx (45231 bytes, 42 blocks)