菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/comol/ai_rules_1c --skill md-to-docx命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
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.
1C configuration repository (хранилище конфигурации) operations — status, history, diff, lock, update, commit, unlock, dump — and the SDLC discipline for repository-bound configurations (lock before edit, commit after verify). Use when .dev.env REPOSITORY_PATH is set or the task mentions the configuration repository / хранилище.
基于 SOC 职业分类
正在显示 SKILL.md
| 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] [--author "Name"] [--title "Title"] [--no-shading]
| 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) |
--author | no | Document author. Written to core properties (dc:creator + cp:lastModifiedBy). Also accepts the --author=Name form |
--title | no | Document title in core properties and in the header. Default: input file name without extension |
--no-shading | no | Disables the grey background for inline code and fenced ``` code blocks. Alias: --shading=off. On by default. Does not affect the table header (it keeps its structural fill) |
If the path is not provided — ask the user. The --author, --title, --no-shading flags are optional — pass them only when the user explicitly asks for an author, a custom title, or removal of code shading.
docx — pinned by this skill's package-lock.json; install locally with npm ci --prefix "<skill-dir>"<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):
npm ci --prefix "<skill-dir>"
node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]"
# With author and title
node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]" --author "I. Ivanov" --title "Analytical note"
# Without the grey code background
node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]" --no-shading
Bash (macOS / Linux):
npm ci --prefix "<skill-dir>"
node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]"
code, links<a id="name"></a> before a heading becomes a bookmark; [text](#name) links resolve to it (external http(s) / mailto: links stay external)) — resolved relative to the source MD folder---)--author / --title)If an image is not found — a red text placeholder is inserted.
Created: output.docx (45231 bytes, 42 blocks)