word-document-processor — Claude Code skill for .docx files

What word-document-processor does

The skill covers three jobs: read a .docx, create a new one, and edit an existing one. For reading, text goes out to markdown through pandoc with --track-changes=all, so insertions and deletions stay visible. Comments, embedded images and metadata need raw XML instead: unpack with python ooxml/scripts/unpack.py <office_file> <output_directory> and read the parts directly. Main content sits in word/document.xml, comments in word/comments.xml, media in word/media/, and tracked changes use <w:ins> and <w:del> tags.

New documents are built with docx-js. You write a JavaScript or TypeScript file out of Document, Paragraph and TextRun components, then export through Packer.toBuffer(). Editing goes through the Python Document library, which handles the unpack and pack steps and still lets you reach the DOM when a case gets messy. Either way the skill insists you read docx-js.md or ooxml.md in full first.

Reviewing someone else's document is its own path. Changes get planned in markdown, then applied to OOXML in batches of 3–10, with each batch tested before the next one starts. Only the text that actually changes gets marked; unchanged runs keep their original RSID, because a redline full of untouched words is painful to review. For legal, academic, business and government documents this path is required. Install runs through npx skills add, and the license is proprietary.