How do I install the DOCX Editor skill?

Run npx skillmds@latest add firstp1ck/docx-editor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is DOCX Editor safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with DOCX Editor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is DOCX Editor free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published DOCX Editor?

Firstp1ck (@firstp1ck) published this skill. Their other Agent Skills are listed on their SkillMD profile.

DOCX Editor by firstp1ck — Agent Skill

Name: DOCX Editor
Rating: 4.2 (5 reviews)
Author: Firstp1ck

DOCX Editor

Safely inspect, search, render, edit, diff, validate, and commit Microsoft Word DOCX files with the dedicated docx_* tools. Use for DOCX/DOTX/DOCM/DOTM document work; enforces dry-run-first edits, active-content refusal, preservation checks, and save-as by default.

Firstp1ck Updated Sep 22, 2026

File contents

DOCX editor

Required workflow

Call docx_inspect before editing an unfamiliar document. Keep sourceSha256, feature/security inventory, and capability report.
Call docx_read for only the relevant stories/blocks. Use returned paragraph IDs, paths, hashes, bookmarks, controls, or strict text anchors.
Call docx_render when pagination, layout, tables, images, headers/footers, or formatting matter. Keep page selections small.
Call docx_edit with dryRun: true; use exact preconditions and expected counts. Resolve ambiguity rather than broadening an edit.
Call docx_edit with dryRun: false and expectedSourceSha256 to create a staged revision. This tool must not receive a destination.
Call docx_validate and docx_diff against source and staged paths. Render focused before/after pages for visually sensitive operations.
Call docx_commit to a new .docx path by default.
Overwrite the source only when the user explicitly asked, hashes still agree, every gate passes, and interactive confirmation is available. Require a recovery path in the result.

Safety rules

Never use built-in text edit or write on DOCX/DOCM/DOTX/DOTM.
Never execute macros, OLE, fields, links, DDE, or attached templates. Never claim they were executed or refreshed.
Treat .docm/.dotm, active content, and signatures as read/render only. Do not bypass SIGNED_DOCUMENT or ACTIVE_CONTENT_BLOCKED.
Do not mutate raw XML, XPath, arbitrary ZIP parts, or page-number selectors.
Do not silently convert formats. Legacy/template conversion must create a new .docx and report losses.
Stop on LOSSY_OPERATION, protected-part changes, unavailable mandatory engines, validation failures, source/destination conflicts, or ambiguous selectors.
Keep hidden/deleted metadata out of model-visible output unless the user explicitly asks to inspect it.

Verification

A successful tool return is not enough. Confirm source and staged/output hashes, declared changed parts, protected-part stability, Open XML validation, independent reopen, semantic diff, and required render checks. Report renderer/font warnings and any host gate that was not run.

---name: docx-editordescription: Safely inspect, search, render, edit, diff, validate, and commit Microsoft Word DOCX files with the dedicated docx_* tools. Use for DOCX/DOTX/DOCM/DOTM document work; enforces dry-run-first edits, active-content refusal, preservation checks, and save-as by default.license: MIT---# DOCX editor## Required workflow1. Call `docx_inspect` before editing an unfamiliar document. Keep `sourceSha256`, feature/security inventory, and capability report.2. Call `docx_read` for only the relevant stories/blocks. Use returned paragraph IDs, paths, hashes, bookmarks, controls, or strict text anchors.3. Call `docx_render` when pagination, layout, tables, images, headers/footers, or formatting matter. Keep page selections small.4. Call `docx_edit` with `dryRun: true`; use exact preconditions and expected counts. Resolve ambiguity rather than broadening an edit.5. Call `docx_edit` with `dryRun: false` and `expectedSourceSha256` to create a staged revision. This tool must not receive a destination.6. Call `docx_validate` and `docx_diff` against source and staged paths. Render focused before/after pages for visually sensitive operations.7. Call `docx_commit` to a new `.docx` path by default.8. Overwrite the source only when the user explicitly asked, hashes still agree, every gate passes, and interactive confirmation is available. Require a recovery path in the result.## Safety rules- Never use built-in text `edit` or `write` on DOCX/DOCM/DOTX/DOTM.- Never execute macros, OLE, fields, links, DDE, or attached templates. Never claim they were executed or refreshed.- Treat `.docm`/`.dotm`, active content, and signatures as read/render only. Do not bypass `SIGNED_DOCUMENT` or `ACTIVE_CONTENT_BLOCKED`.- Do not mutate raw XML, XPath, arbitrary ZIP parts, or page-number selectors.- Do not silently convert formats. Legacy/template conversion must create a new `.docx` and report losses.- Stop on `LOSSY_OPERATION`, protected-part changes, unavailable mandatory engines, validation failures, source/destination conflicts, or ambiguous selectors.- Keep hidden/deleted metadata out of model-visible output unless the user explicitly asks to inspect it.## VerificationA successful tool return is not enough. Confirm source and staged/output hashes, declared changed parts, protected-part stability, Open XML validation, independent reopen, semantic diff, and required render checks. Report renderer/font warnings and any host gate that was not run.

Frequently asked questions