openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing,…
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.
$ npx -y skills add comol/ai_rules_1c --skill md-to-docx --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/md-to-docxContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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] [--justify]
| 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) | | `--justify` | no | Justifies body paragraphs and list items, including block quotes. Alias: `--align=justify` (also `--align justify`). Off by default; headings, code blocks, table cells and image captions keep their alignment |
If the path is not provided — ask the user. The `--author`, `--title`, `--no-shading`, `--justify` flags are optional — pass them only when the user explicitly asks for an author, a custom title, removal of code shading, or justified text.
`<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 # With justified body text node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]" --justify
Bash (macOS / Linux):
npm ci --prefix "<skill-dir>" node "<skill-dir>/scripts/md_to_docx.js" "<input.md>" "[output.docx]"
If an image is not found — a red text placeholder is inserted.
Created: output.docx (45231 bytes, 42 blocks)
Repo: comol/ai_rules_1c
Implement tasks from an OpenSpec change. Use when the user wants to start implementing,…
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to…
Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems,…
Propose a new OpenSpec change with all artifacts generated in one step. Use when the user…
Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update…
Update an OpenSpec change by revising its existing planning artifacts and keeping them…