Word Documents

What it does

Word Documents addresses the structure behind editable .docx files, not just text generation. The reviewed source separates creating a new document, reading content and editing an existing package. New documents use docx-js; existing files require preserving their XML package structure. It also explains document-specific failure modes such as tables with incorrect widths, invisible comment anchors and tracked changes that do not cover all edits.

When to use it

• Create a structured client report with real heading levels, a table of contents, consistent tables and page numbers.
• Revise an existing Word agreement while preserving its structure and identifying tracked edits.
• Read a Word document or add comments that remain visible in the document application.

Step-by-step workflow

1. Choose the task: create, extract, edit, annotate or redline. Preserve the original file and work on a copy when modifying an existing document.
2. For creation, use actual heading levels, correct page dimensions, configured list numbering and consistent table/cell widths. These affect Word behavior as well as appearance.
3. For existing files, inspect and edit the document package with the supplied workflow. The reviewed source notes that docx-js does not open existing files for editing.
4. Handle comments and tracked changes with the required relationships and XML markers. A comment record without its text anchor can exist without appearing to the reader.
5. Validate the output and render pages for inspection. Compare page breaks, table layout, numbering and revision visibility with the intended result.

Example request

Use the Word Documents skill to create a six-page project proposal from brief.md. Use A4 pages, built-in heading levels, a table of contents, a milestone table and page numbers. Keep the document editable. Render every page for inspection and correct clipped tables or awkward page breaks. Return the .docx, a PDF preview and the validation result. Do not overwrite the source brief.

Worked example

A milestone table can look correct in generated XML yet render beyond the page margin when table and cell widths disagree. A useful check renders the file and inspects each page. For a revision task, also compare content with the original: attractive formatting cannot compensate for accidentally removing a clause or accepting changes that should remain visible.

What you get

An editable .docx document or a reviewed edit to an existing Word file.

How to evaluate the result

• Expect an editable document plus the requested preview, with validation results and any unresolved formatting limitations.
• Inspect all pages, especially long tables, headings near page boundaries, footers and numbered lists. Check the table of contents in the target application.
• For redlining, verify authorship and coverage of changes against the original. Preserve an untouched source for comparison.

What you need

Source text or documents and the document tooling required by the selected workflow.

Setup and activation

The publisher README groups Word Documents under the document-skills plugin for Claude Code and describes hosted Claude document capabilities. Check the restrictive LICENSE.txt and your Anthropic agreement before adopting or copying materials. Creation, reading and editing require different tools; verify the dependencies for the chosen path rather than assuming the hosted environment matches a local computer. This page installs nothing. Before local installation, review and security-scan the exact source/version; catalogue inclusion is not security approval.

Limits and considerations

The skill has restrictive source-available terms; public GitHub access does not grant unrestricted redistribution or use. Its tooling assumptions include docx-js, Pandoc, LibreOffice and Poppler depending on the workflow. Availability in a hosted environment does not mean those dependencies exist on your computer.

Related workflows

• Use a document review process for legal or contractual substance.
• Keep visual inspection separate from XML/schema validation; both catch different failures.

License and reuse

Proprietary / source-available; see LICENSE.txt.

Further reading

• Publisher setup and repository README
• Skill-specific license