[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.
日本語の概要は準備中です。原文の説明を表示しています。
[Document Processing] Use when converting between Word DOCX and Markdown (GFM, math rendering). --to={markdown|docx}.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Goal: Convert Word DOCX to Markdown, or Markdown to Word DOCX, through one entry point.
Workflow:
--to markdown (DOCX in, Markdown out) or --to docx (Markdown in, DOCX out)package.json; install only the one you needscripts/convert.cjs --to <direction> with the direction's own optionsKey Rules:
--to is required. There is no default direction — converting the wrong way silently is worse than an error.--to markdown never pulls in the DOCX writer, and vice versa.Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
--to markdown)--to docx)Convert Microsoft Word (.docx) files to GitHub-Flavored Markdown, and Markdown files to editable Word documents with tables, code blocks, images and LaTeX math.
| Flag | Converts | Lives in | Dependencies |
|---|---|---|---|
--to markdown | DOCX → Markdown | to-markdown/ | mammoth, turndown, turndown-plugin-gfm |
--to docx | Markdown → DOCX | to-docx/ | markdown-docx, gray-matter |
Each direction installs separately. Install only the one you need:
# DOCX -> Markdown
cd .claude/skills/docx-convert/to-markdown
npm install
# Markdown -> DOCX
cd .claude/skills/docx-convert/to-docx
npm install
ck init (which runs install.sh) handles every skill at once.
# DOCX -> Markdown
node .claude/skills/docx-convert/scripts/convert.cjs --to markdown --input ./document.docx
# DOCX -> Markdown, extracting images to a folder instead of inlining base64
node .claude/skills/docx-convert/scripts/convert.cjs --to markdown -i ./doc.docx --images ./images/
# Markdown -> DOCX
node .claude/skills/docx-convert/scripts/convert.cjs --to docx --input ./README.md
# Markdown -> DOCX with a custom theme
node .claude/skills/docx-convert/scripts/convert.cjs --to docx -i ./doc.md --theme ./theme.json
--to=markdown and --to markdown are equivalent. A missing or unknown --to prints the valid
directions and exits 1.
| Option | Description | Default |
|---|---|---|
--to | Conversion direction: markdown or docx | (required) |
--to markdown (DOCX → Markdown)| Option | Short | Description | Default |
|---|---|---|---|
--input | -i | Input DOCX file path | (required) |
--output | -o | Output markdown file path | {input}.md |
--images | Directory for extracted images | inline base64 | |
--help | -h | Show help message |
--to docx (Markdown → DOCX)| Option | Short | Description | Default |
|---|---|---|---|
--input | -i | Input markdown file | (required) |
--output | -o | Output DOCX path | {input}.docx |
--theme | -t | Custom theme JSON | built-in |
--title | Document title | filename | |
--help | -h | Show help |
Run scripts/convert.cjs --to <direction> --help to see a direction's full help.
DOCX → Markdown
Markdown → DOCX
$...$, $$...$$)Both directions work on Windows, macOS and Linux.
--to markdown)DOCX → mammoth → HTML → turndown → Markdown
The two-stage conversion follows mammoth's official recommendation for best results.
Both directions return JSON on success:
{
"success": true,
"input": "/path/to/input.docx",
"output": "/path/to/output.md",
"stats": {
"images": 3,
"tables": 2,
"headings": 5
}
}
--to docx omits stats. On failure both return { "success": false, "error": "..." } and exit 1.
--to docx)Generated DOCX files open in Microsoft Word (2007+), Google Docs, LibreOffice Writer and Apple Pages.
Missing dependencies: the error output carries a hint with the exact cd … && npm install
command for the direction you invoked.
cd .claude/skills/docx-convert && node tests/dispatcher.test.cjs # routing and --to validation
cd .claude/skills/docx-convert/to-markdown && node tests/run-tests.cjs
cd .claude/skills/docx-convert/to-docx && node tests/run-tests.cjs
[IMPORTANT] Use
TaskCreateto break ALL work into small tasks BEFORE starting. This prevents context loss from long files. Keep task depth proportional to the work.
IMPORTANT MUST ATTENTION Goal: Convert Word DOCX to Markdown, or Markdown to Word DOCX, through one entry point — scripts/convert.cjs --to {markdown|docx}.
IMPORTANT MUST ATTENTION --to is required — never guess the direction for the user
IMPORTANT MUST ATTENTION each direction installs its own dependencies; the error hint names the exact directory
IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
IMPORTANT MUST ATTENTION add a final review todo task to verify work quality
[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when a workflow step or the user asks for architecture design, compliance review, scalability grading or whole-project audit via --mode={design|review|scalability|full}.
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.
日本語の概要は準備中です。原文の説明を表示しています。