Agent skill · writing content · borghei
docx-toolkit
Audit Microsoft Word (.docx) documents for heading hierarchy, comments, tracked changes, broken cross-references, and style consistency. Use when reviewing a contract draft, preparing a document for handoff, or enforcing a style guide.
Why this skill is useful
Adds a specialized Python script for auditing .docx files that includes specific checks for document quality and style compliance.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Docx Toolkit Audit .docx files using the standard library only — no python-docx required. Reads OOXML directly with zipfile + xml.etree. --- Table of Contents Keywords Quick Start Core Workflows Tools Reference Guides Templates Best Practices --- Keywords docx, Word, Microsoft Word, document, document review, comments, tracked changes, redline, headings, style guide, word count, document audit --- Clarify First Before running the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Audit purpose (pre-handoff cleanup, contract-review triage, or style-guide enforcement) — selects the workflow and the thresholds you apply [ ] Recipient (external customer, opposing counsel, internal) — sets the tolerance for leftover comments and tracked changes [ ] Allowed style set (for style-guide enforcement) — defines what counts as a non-conforming style Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Quick Start Outputs: word count, paragraph count, heading hierarchy, comment count, tracked-changes status, hyperlink count, list of unique paragraph styles used. --- Core Workflows Workflow 1: Pre-Handoff Document Audit Goal: Catch the issues that embarrass a sender — leftover comments, unresolved track changes, broken heading hierarchy — before the document leaves. Steps: 1. Run: python scripts/docxauditor.py document.docx 2. Review the audit output: Comment count > 0 → resolve or remove before sending Tracked changes detected → accept or reject before sending Heading-hierarchy gaps (H1 → H3 with no H2) → restructure Style sprawl (more than 8 paragraph styles) → consolidate 3. Re-run until clean Time Estimate: 5-15 minutes per document. Workflow 2: Contract Review Triage Goal: Quantify how much rework a returned contract needs before reading it line-by-line. Steps: 1. Run audit on the returned .docx 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/docx-toolkit