Docx Tool
Inspect, search, read, edit, comment, accept supported tracked changes in, convert, and export Microsoft Word DOCX documents with the docx-tool CLI. Use when an agent must work with DOCX paragraphs, tables, cells, content controls, checkboxes, comments, images, or revisions while keeping reads bounded, using one-based addresses, applying edits transactionally, and verifying the output.
Install
$ agentstack add skill-evrenverse-docx-tool-docx-tool ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-evrenverse-docx-tool-docx-tool) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
DOCX Tool
Use docx-tool instead of writing a one-off Word-processing script.
Prepare
- Run
command -v docx-tool. - If missing and this repository is available, run
uv tool install ..
Otherwise run uv tool install git+https://github.com/evrenverse/docx-tool.
- Run
docx-tool --version. - Run
docx-tool capabilities --jsonanddocx-tool doctor --json. - Use
docx-tool schemawhen constructing structured input. - Work on a copy unless the user explicitly wants an in-place edit.
Inspect before editing
- Run
docx-tool info --json. - Use
find,read --paragraphs, orread --table --cells. - Remember that all DOCX addresses are one-based.
- Avoid an unscoped full read when bounded content is enough.
Edit and verify
- Prefer one
writeorbatchoperation for related edits. - Treat any failed operation as a failed transaction; the CLI writes nothing.
- Read every changed paragraph or table cell back with
--json. - Report the output path and any round-trip limitation.
Use comment only for an entire ordinary body paragraph. Inspect revisions before accept-changes; that command aborts if unsupported change markup remains. Do not use this CLI to rewrite a digitally signed DOCX.
Read [references/cli.md](references/cli.md) when exact syntax, operation schemas, or LibreOffice requirements are needed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: evrenverse
- Source: evrenverse/docx-tool
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.