# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-evrenverse-docx-tool-docx-tool`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [evrenverse](https://agentstack.voostack.com/s/evrenverse)
- **Installs:** 0
- **Category:** [Search](https://agentstack.voostack.com/c/search)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [evrenverse](https://github.com/evrenverse)
- **Source:** https://github.com/evrenverse/docx-tool/tree/main/skills/docx-tool

## Install

```sh
agentstack add skill-evrenverse-docx-tool-docx-tool
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# DOCX Tool

Use `docx-tool` instead of writing a one-off Word-processing script.

## Prepare

1. Run `command -v docx-tool`.
2. If missing and this repository is available, run `uv tool install .`.
   Otherwise run `uv tool install git+https://github.com/evrenverse/docx-tool`.
3. Run `docx-tool --version`.
4. Run `docx-tool capabilities --json` and `docx-tool doctor --json`.
5. Use `docx-tool schema ` when constructing structured input.
6. Work on a copy unless the user explicitly wants an in-place edit.

## Inspect before editing

1. Run `docx-tool info  --json`.
2. Use `find`, `read --paragraphs`, or `read --table --cells`.
3. Remember that all DOCX addresses are one-based.
4. Avoid an unscoped full read when bounded content is enough.

## Edit and verify

1. Prefer one `write` or `batch` operation for related edits.
2. Treat any failed operation as a failed transaction; the CLI writes nothing.
3. Read every changed paragraph or table cell back with `--json`.
4. 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](https://github.com/evrenverse)
- **Source:** [evrenverse/docx-tool](https://github.com/evrenverse/docx-tool)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-evrenverse-docx-tool-docx-tool
- Seller: https://agentstack.voostack.com/s/evrenverse
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.