Agent skill · Code Review & Quality

docx-processing-superdoc

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface. Use when the user asks to read, search, modify, comment, or review changes in .docx files.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill word-editor-superdoc --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 5 KB
Bundled scripts: none
Version: 2026.03.18
Declared author: Superdoc
Path: skills/word-editor-superdoc/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SuperDoc CLI (v1) Use SuperDoc CLI for DOCX work. Use v1 commands (canonical operations and their helper wrappers). Do not default to legacy commands unless explicitly needed for v0-style bulk workflows. Use `superdoc` if installed, or `npx @superdoc-dev/cli@latest` as a fallback. ## First Step: Discover Exact Params For unknown commands or flags, inspect runtime metadata first: ```bash superdoc describe superdoc describe command find superdoc describe command "comments add" ``` Use `describe command` for per-command args and constraints. ## Preferred Workflows ### 1) Stateful multi-step edits (recommended) ```bash superdoc open ./contract.docx superdoc query match --select-json '{"type":"text","pattern":"termination"}' --require exactlyOne superdoc replace --target-json '{"kind":"text","blockId":"p1","range":{"start":0,"end":11}}' --text "expiration" superdoc save --in-place superdoc close ``` - Always use `query match` (not `find`) to discover mutation targets — it returns exact addresses with cardinality guarantees. - After `open`, commands run against the active/default session when `<doc>` is omitted. - Use `superdoc session list|set-default|save|close` for explicit session

What's inside
Steps it walks through
  1. First Step: Discover Exact Params
  2. Preferred Workflows
  3. 1) Stateful multi-step edits (recommended)
  4. 2) Stateless one-off reads
  5. 3) Stateless one-off mutations
  6. Safety: preview before apply
  7. Common v1 Commands
  8. Query & inspect
  9. Mutate
  10. Format
  11. Lists
  12. Comments
  13. Track changes
  14. History
Ships with 2 files
  • LICENSE.txt
  • README.md
Commands it runs
superdoc describe
superdoc describe command find
superdoc describe command "comments add"
superdoc open ./contract.docx
superdoc query match --select-json '{"type":"text","pattern":"termination"}' --require exactlyOne
superdoc replace --target-json '{"kind":"text","blockId":"p1","range":{"start":0,"end":11}}' --text "expiration"
superdoc save --in-place
superdoc close
superdoc get-text ./proposal.docx
superdoc get-markdown ./proposal.docx
More from awesome-legal-skills
All skills →
About this skill
What does the docx-processing-superdoc skill do?

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface. Use when the user asks to read, search, modify, comment, or review changes in .docx files.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill word-editor-superdoc --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 lawve-ai/awesome-legal-skills, a repository with 618 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.

Keep going