LLM Skills
~/catalog/automated workflows//SKILL
Automated workflowsGitHub source

Docx

/SKILL

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

Prat011Prat011
1.4k
April 22, 2026
// skill content

--- name: docx description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks" license: Proprietary. LICENSE.txt contains the full terms --- # DOCX creation, editing, and analysis ## Overview A user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks. ## Workflow Decision Tree ### Reading/Analyzing Content Use the "Text extraction" or "Raw XML access" sections below ### Creating a New Document Use "Creating a new Word document" workflow ### Editing an Existing Document - Your own document + simple changes Use the “Basic OOXML editing” workflow - Someone else’s document Use “Redlining workflow” (recommended default) - Legal, academic, business, or government documents Use “Redlining workflow” (required) ## Reading and analyzing content ### Text extraction If you just need to read the text contents of a document, you should convert the document to Markdown using pandoc. Pandoc provides excellent support for preserving document structure and can display tracked changes: ``bash # Convert document to markdown with tracked changes pandoc --track-changes=all path-to-file.docx -o output.md # Options: --track-changes=accept/reject/all ### Raw XML access You need raw XML access for: comments, complex formatting, document structure, embedded media, and metadata. For any of these features, you'll need to unpack a document and read its raw XML contents. #### Unpacking a file python ooxml/scripts/unpack.py<officefile><outputdirectory> #### Key file structures * word/document.xml - Main document contents * word/comments.xml - Comments referenced in document.xml * word/media/ - Embedded images and media files * Tracked changes use <w:ins> (insertions) and <w:del> (deletions) tags ## Creating a new Word document When creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript. ### Workflow 1. **MANDATORY - READ ENTIRE FILE**: Read [docx-js.md](docx-js.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with document creation. 2. Create a JavaScript/TypeScript file using Document, Paragraph, TextRun components (You can assume all dependencies are installed, but if not, refer to the dependencies section below) 3. Export as .docx using Packer.toBuffer() ## Editing an existing Word document When editing an existing Word document, use the **Document library** (a Python library for OOXML manipulation). The library automatically handles infrastructure setup and provides methods for document manipulation. For complex scenarios, you can access the underlying DOM directly through the library. ### Workflow 1. **MANDATORY - READ ENTIRE FILE**: Read [ooxml.md](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for the Document library API and XML patterns for directly editing document files. 2. Unpack the document: python ooxml/scripts/unpack.py<officefile><outputdirectory> 3. Create and run a Python script using the Document library (see "Document Library" section in ooxml.md) 4. Pack the final document: python ooxml/scripts/pack.py<inputdirectory><officefile>` The Document Library provides both high-level methods for common operations and direct DOM access for complex scenarios. ## Redlining workflow for document review This workflow allows you to plan comprehensive tracked changes using Markdown before implementing them in OOXML. CRITICAL: For complete tracked changes,

// original public source
Prat011/awesome-llm-skills
/document-skills/docx/SKILL.md
License: License not specified. Review the repository before reusing it.
Independent project, not affiliated with Anthropic. This skill remains the property of its original author.
// install this skill
Paste this command in your terminal at the root of your project:
mkdir -p .claude/commands && curl -o ".claude/commands/SKILL.md" "https://raw.githubusercontent.com/Prat011/awesome-llm-skills/master/document-skills/docx/SKILL.md"
Then in Claude Code, type /SKILL to activate it.
open_in_newOpen original source
// save
Save available after sign in.
loginSign in to save
// information
CreatorPrat011
Stars 1.4k
UpdatedApril 22, 2026
Format.md
AccessFree
// similar

Skills Automated workflows

View allarrow_forward