home / skills / henkisdabro / wookstar-claude-plugins / docx

This skill helps you create, edit, and analyze Word documents (.docx) with tracked changes, comments, and formatting preservation for professional workflows.

npx playbooks add skill henkisdabro/wookstar-claude-plugins --skill docx

Review the files below or copy the command above to add this skill to your agents.

Files (60)
SKILL.md
6.3 KB
---
name: docx
description: Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when working with professional documents (.docx files) for creating new documents, modifying or editing content, working with tracked changes, adding comments, or any other document tasks. Do NOT use for creating proposals, letters, or client-facing business documents from scratch - use document-builder for those.
---

# DOCX creation, editing, and analysis

## Overview

A user may ask you to create, edit, or analyse 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/Analysing Content

Use "Text extraction" or "Raw XML access" sections below

### Creating New Document

Use "Creating a new Word document" workflow

### Editing Existing Document

- **Your own document + simple changes**
  Use "Basic OOXML editing" workflow

- **Someone else's document**
  Use **"Redlining workflow"** (recommended default)

- **Legal, academic, business, or government docs**
  Use **"Redlining workflow"** (required)

## Reading and analysing 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 show 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 <office_file> <output_directory>`

#### 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 <office_file> <output_directory>`
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 <input_directory> <office_file>`

The Document library provides both high-level methods for common operations and direct DOM access for complex scenarios.

## Redlining workflow for document review

Use this workflow when editing someone else's document or any formal/professional document. It implements tracked changes (redlining) so the document owner can review and accept/reject each change.

**Key principles**: Group changes into batches of 3-10. Only mark text that actually changes - never replace entire sentences when only a word changes. Preserve original run RSIDs for unchanged text.

**MANDATORY**: Before starting, read the full workflow in [`references/redlining-workflow.md`](references/redlining-workflow.md) for the complete step-by-step process, batching strategies, minimal edit principles with examples, and verification steps.

**Quick summary of steps**: Convert to markdown, identify and group changes, read ooxml.md, unpack document, implement changes in batches using the Document library, pack the result, and verify all changes.

## Converting Documents to Images

To visually analyse Word documents, convert them to images using a two-step process:

1. **Convert DOCX to PDF**:
   ```bash
   soffice --headless --convert-to pdf document.docx
   ```

2. **Convert PDF pages to JPEG images**:
   ```bash
   pdftoppm -jpeg -r 150 document.pdf page
   ```
   This creates files like `page-1.jpg`, `page-2.jpg`, etc.

Options:
- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)
- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
- `page`: Prefix for output files

Example for specific range:
```bash
pdftoppm -jpeg -r 150 -f 2 -l 5 document.pdf page  # Converts only pages 2-5
```

## Code Style Guidelines

**IMPORTANT**: When generating code for DOCX operations:
- Write concise code
- Avoid verbose variable names and redundant operations
- Avoid unnecessary print statements

## Dependencies

Required dependencies (install if not available):

- **pandoc**: `sudo apt-get install pandoc` (for text extraction)
- **docx**: `npm install -g docx` (for creating new documents)
- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
- **defusedxml**: `pip install defusedxml` (for secure XML parsing)

Overview

This skill provides comprehensive creation, editing, and analysis capabilities for .docx files, including tracked changes (redlining), comments, formatting preservation, and text extraction. It supports workflows for creating new documents, making precise edits to existing files, unpacking raw OOXML for advanced manipulation, and converting pages to images for visual review. Use it when you need reliable, programmatic control over professional Word documents.

How this skill works

The skill uses a mix of tools and libraries: pandoc for clean text extraction (with tracked change visibility), a Document library for Python-based OOXML manipulation, and docx-js for authoring new documents in JavaScript/TypeScript. For deep inspection, it unpacks the .docx ZIP and exposes key XML files (e.g., word/document.xml, word/comments.xml) so you can read or modify runs, comments, and tracked-change tags. It also provides commands for converting DOCX→PDF (LibreOffice) and PDF→images (pdftoppm) for visual analysis.

When to use it

  • You need to review or edit someone else’s formal document while preserving redline history
  • You must inspect comments, embedded media, or complex formatting at the XML level
  • You want to extract document text with tracked changes visible
  • You need to create a programmatic .docx template or generate documents via code
  • You want to convert document pages to images for QA or screenshots

Best practices

  • Always read the indicated full reference workflow files before major operations (creation, editing, redlining) to avoid partial edits
  • Use the redlining workflow for external, legal, academic, or government documents to preserve change history
  • Batch edits into small groups (3–10 changes) and only change the minimal text necessary
  • Prefer pandoc for text extraction and structure-preserving conversions
  • When editing, unpack the .docx and verify changes against document.xml and comments.xml before repacking

Example use cases

  • Apply tracked-change edits and comments to a client-supplied contract for review
  • Extract a long report to markdown while preserving insertion/deletion marks
  • Programmatically generate a formatted internal template using docx-js
  • Unpack a document to replace or inspect embedded images and media files
  • Convert a multi-page report to JPEGs for visual QA and annotation

FAQ

Can I accept or reject tracked changes automatically?

Yes — you can manipulate <w:ins> and <w:del> tags or use the Document library API to accept/reject, but follow the redlining workflow and verify changes in batches.

Which tool should I use to extract text with tracked changes visible?

Use pandoc with --track-changes=all (or accept/reject) to convert the .docx to markdown while preserving change marks.