docx
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Profile →npx skills add opensquilla/opensquilla --skill docx --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# docx Work with Microsoft Word `.docx` files. The format is OOXML — a zip container holding XML parts (`word/document.xml`, `styles.xml`, `numbering.xml`, headers, footers, relationships). Treat structure as primary; rendered text is a view. ## Decide the path first Pick **one** path up front. The right path depends only on what is on disk before you start. | You have | Goal | Path | |---|---|---| | Existing `.docx` | Read text/structure | A. Inspect | | Existing `.docx` | Modify content while keeping styles | B. Edit-in-place | | Nothing or a brief | Build a new doc | C. Create from scratch | If the user hands you a doc and asks for changes, default to path B and treat the input as the visual style baseline. Only choose path C when the user says "start fresh" or there is no input. --- ## Path A: Inspect Dump structure as JSON for inspection without mutating anything. ```bash python {baseDir}/scripts/inspect_docx.py /path/to/doc.docx ``` Output schema: ```json { "paragraphs": [{"index": 0, "text": "...", "style": "Heading 1"}, ...], "tables": [[["row0,col0", "row0,col1"], ...], ...], "sections": 1, "has_tracked_changes": false } ``` Use this whenever you need to see what is in the
- Decide the path first
- Path A: Inspect
- Path B: Edit in place
- B1. Run-level text replacement (preferred)
- B2. Structural edits (sections / page layout / numbering)
- Path C: Create from scratch
- Tracked changes
- Common pitfalls
- Boundaries
python {baseDir}/scripts/inspect_docx.py /path/to/doc.docx
python {baseDir}/scripts/edit_docx.py input.docx ops.json --out output.docx
mkdir _unpacked && (cd _unpacked && unzip -q ../input.docx)
edit _unpacked/word/document.xml
python {baseDir}/scripts/create_docx.py spec.json --out out.docxWhat does the docx skill do?
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill docx --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.