Anthropic DOCX
Create Word files, edit existing documents, and work with comments and tracked changes.
npx skills add anthropics/skills --skill docxClaude skills for Word documents: create files, edit existing documents, and work with comments and tracked changes.
Create Word files, edit existing documents, and work with comments and tracked changes.
npx skills add anthropics/skills --skill docxCreate, edit, and validate DOCX files in a workflow that also supports PDF, DOCX, XLSX, and PPTX.
A Word file breaks in ways plain text never does: comments get orphaned, tracked changes are accepted without anyone deciding, and named styles collapse into direct formatting. A Claude DOCX skill exists to run those steps in order and to keep a copy you can compare against the original.
Editing a contract, a memo or a report someone else owns means the reviewer has to see what changed. The Anthropic DOCX skill can produce edits as tracked changes rather than flat replacements, so a Word reviewer accepts or rejects each one. Ask for markup in the request itself: a prompt that only says "edit this document" can come back merged. State the target sentence and the replacement, and ask for tracked changes before the edit runs.
Review threads are the part of a Word file an agent most often drops. If a document carries comments that must survive, say so and check the comment pane after the edit. When a thread is settled, the reviewer still decides whether to resolve it: deleting comments during an automated edit removes the record of who asked for what.
Word stores heading levels, list numbering and section breaks in the file structure, not in the visible text. Edits that only replace text usually keep them; edits that rebuild paragraphs can reset numbering to 1 or push a heading from Heading 2 to direct formatting. After the edit, check one numbered list, one table of contents entry and the page break before each section. If the document has a table of contents, refresh it in Word before sharing.
Use the Documents skill by magnus919 when the same content has to leave as Word and as a PDF report or a spreadsheet. It runs one workflow across DOCX, XLSX, PPTX and PDF, which keeps shared numbers and wording consistent. The trade-off is depth: for a Word-only job with heavy review markup, the format-specific skill gives you more control over comments and tracked changes.
Use a dedicated Word skill when tracked changes, comments or precise document structure matter. Use a cross-format workflow when the same content must go out in Word and other files. Whichever you pick, ask for the output as a file path so you can open it in Word rather than trusting a summary of the edit.
Open the finished DOCX in Word and review headings, page breaks, comments and markup. For an edited document, compare it with the source. Check that the font and style names survived, and that no comment thread disappeared during the edit.
Start with Anthropic DOCX. Ask for tracked changes explicitly in the request, then open the result in Word with All Markup enabled and confirm each edit is listed as a revision rather than applied silently.
Yes, if you give it the existing file and say which parts should change. Keep a copy of the original, ask for tracked changes, and diff the two versions before you send anything on.
Text replacements usually keep them, but paragraph rebuilds can reset list numbering or replace named styles with direct formatting. Check one numbered list and the table of contents after the edit, and refresh the contents in Word.
A Word-specific skill usually stays with DOCX. If one piece of content has to go out as Word and PDF, use the multi-format Documents skill instead of running two separate edits.
Open the comment pane in Word and count the threads against the source file. Automated edits that delete resolved comments can erase the reviewer's history, so list the comments that must stay before you run the skill.