Agent skill

DOCX Processing Superdoc

by lawve-ai in lawve-ai/awesome-legal-skills

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface.

AGPL-3.0Auto-check passedDocuments & Office

Install DOCX Processing Superdoc

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/word-editor-superdoc .claude/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .claude/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/word-editor-superdoc .agents/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .agents/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/word-editor-superdoc .cursor/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .cursor/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/lawve-ai/awesome-legal-skills.git --path skills/word-editor-superdoc

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/word-editor-superdoc .gemini/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .gemini/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/word-editor-superdoc .github/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .github/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install lawve-ai/awesome-legal-skills docx-processing-superdoc --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/word-editor-superdoc .opencode/skills/docx-processing-superdoc && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "docx-processing-superdoc" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/word-editor-superdoc into .opencode/skills/docx-processing-superdoc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docx-processing-superdoc", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: docx-processing-superdoc
GitHub stars: 836
Token cost: ~1.4k tokens
SKILL.md length: 493 words
Files: 3
Skills in repo: 154
Repo updated: Oct 2, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface.

Works in 3 steps: Stateful multi-step edits (recommended) → Stateless one-off reads → Stateless one-off mutations
The user asks to read
SKILL.md covers First Step: Discover Exact…, Preferred Workflows, Common v1 Commands and JSON/File Payload Flags, plus 2 more sections
Calls npx

What it does

DOCX Processing Superdoc is an agent skill from lawve-ai/awesome-legal-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md`).

It sits in Documents & Office, covering Word documents. It works with Microsoft Word. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is AGPL-3.0.

When your agent uses it

The user asks to read
Review changes in .docx files

Example prompts

“/docx-processing-superdoc”

Requirements

Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Stateful multi-step edits (recommended)
Stateless one-off reads
Stateless one-off mutations

What it can do on your machine

Read from SKILL.md and the folder at commit 045f738. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

DOCX Processing Superdoc loads about 1.4k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~50
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from lawve-ai/awesome-legal-skills at commit 045f738, republished under its AGPL-3.0 licence (© lawve-ai). 493 words, ~1,367 tokens.

Download SKILL.mdSave it as .claude/skills/docx-processing-superdoc/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: docx-processing-superdoc
description: 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.
metadata.author: Superdoc
metadata.license: AGPL-3.0
metadata.version: 2026.03.18

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 control.
close on dirty state requires --discard or a prior save.

2) Stateless one-off reads

bash

superdoc get-text ./proposal.docx
superdoc get-markdown ./proposal.docx
superdoc info ./proposal.docx

3) Stateless one-off mutations

bash

superdoc replace ./proposal.docx \
  --target-json '{"kind":"text","blockId":"p1","range":{"start":0,"end":5}}' \
  --text "Updated" \
  --out ./proposal.updated.docx

In stateless mode (<doc> provided), mutating commands require --out unless using --dry-run.

Safety: preview before apply

Use --dry-run to preview any mutation without applying it.
Use --expected-revision <n> with stateful mutations for optimistic concurrency checks.

Common v1 Commands

Query & inspect

Search/browse content: find --type text --pattern "..." or find --query-json '{...}'
Find mutation target: query match --select-json '{...}' --require exactlyOne
Inspect blocks: blocks list, get-node, get-node-by-id
Extract content: get-text, get-markdown, get-html

Mutate

Replace text: replace --target-json '{...}' --text "..."
Insert inline text: insert --block-id <id> --offset <n> --value "..."
Delete text/node: delete --target-json '{...}'
Delete blocks: blocks delete, blocks delete-range
Batch mutations: mutations apply --steps-json '[...]' --atomic true --change-mode direct
Create paragraph: create paragraph --text "..." (with optional --at-json)
Create heading: create heading --input-json '{"level":<n>,"text":"..."}'

Format

Apply formatting: format apply --block-id <id> --start <n> --end <n> --inline-json '{"bold":true}'
Shortcuts: format bold, format italic, format underline, format strikethrough

Lists

List items: lists list, lists get
Insert list item: lists insert --node-id <id> --position after --text "..."
Modify: lists indent, lists outdent, lists set-level, lists set-type, lists convert-to-text

Show full SKILL.md (202 more words)Show less

Comments

Add/reply: comments add, comments reply
Read: comments get, comments list
Edit/resolve/move: comments edit, comments resolve, comments move, comments set-internal
Delete: comments delete (canonical) or comments remove (alias)

Track changes

List: track-changes list, track-changes get
Decide: track-changes accept, track-changes reject, track-changes accept-all, track-changes reject-all

History

history get, history undo, history redo

Low-level

Direct invoke: call <operationId> --input-json '{...}' (JSON output only — --pretty is not supported)

JSON/File Payload Flags

Not all --*-file variants are available on every command. Use describe command <name> to check.

Always supported alongside their -json counterpart (use one, not both):

Flag pair	Available on
`--query-json` / `--query-file`	`find`, `lists list`
`--address-json` / `--address-file`	`get-node`, `lists get`
`--input-json` / `--input-file`	`call`, `create paragraph`
`--at-json` / `--at-file`	`create paragraph`

--target-json is widely available on mutation commands but has no --target-file counterpart. Use flat flags (--block-id, --start, --end) as an alternative to --target-json.

Output and Global Flags

Default output is JSON envelope.
Use --pretty for human-readable output (not supported by call).
Global flags: --output <json|pretty>, --session <id>, --timeout-ms <n>.
<doc> can be - to read DOCX bytes from stdin.

Legacy Compatibility (Use Sparingly)

Legacy v0.x bridge commands still exist:

bash

superdoc search <pattern> <files...>
superdoc replace-legacy <find> <to> <files...>
superdoc read <file>

Use these only when you specifically need v0-style behavior (especially multi-file glob search/replace). For new automations, prefer v1 operations.

Files

SKILL.md and 2 other files in skills/word-editor-superdoc of lawve-ai/awesome-legal-skills.

SKILL.md
LICENSE.txt
README.md

Open the folder on GitHubat commit 045f738

Compare with similar skills

DOCX Processing Superdoc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

DOCX Processing Superdoc compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
DOCX Processing Superdoc this skilllawve-ai/awesome-legal-skills	836	—	~1.4k	Automated safety check: Pass	AGPL-3.0	5 days ago
MarkitdownImCa0/just-laws	781	14 repos	~3.2k	Automated safety check: Notes	MIT	today
DOCXrvdbreemen/OTGW-firmware	207	33 repos	~4.3k	Automated safety check: Pass	Proprietary	yesterday
Gzh Designisjiamu/gzh-design-skill	3.9k	1 repos	~2.2k	Automated safety check: Pass	AGPL-3.0	5 days ago
Word Document Reader and WriterHKUDS/DeepTutor	41k	—	~2.5k	Automated safety check: Pass	Apache-2.0	today
GenOffice Document CLIgenspark-ai/genoffice	8.9k	—	~19k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
781 GitHub starsUsed in 14 repos~3.2k tokens
Documents & OfficeAuto-check: notes
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
207 GitHub starsUsed in 33 repos~4.3k tokens
Documents & OfficeAuto-check passed
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
3.9k GitHub starsUsed in 1 repo~2.2k tokens
Documents & OfficeAuto-check passed
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
41k GitHub stars~2.5k tokensUpdated today
Documents & OfficeAuto-check passed
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
8.9k GitHub stars~19k tokensUpdated today
Documents & OfficeAuto-check passed
BiSheng DOCX Builder
dataelement/bisheng
Builds or edits Word .docx documents inside BiSheng's code executor with python-docx, handling Chinese fonts, tables of contents, page numbers and official-document layout.
12k GitHub stars~2.6k tokensUpdated today
Documents & OfficeAuto-check passed

Questions about DOCX Processing Superdoc

What does DOCX Processing Superdoc do?

Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface. DOCX Processing Superdoc is an agent skill from lawve-ai/awesome-legal-skills. Edit, query, and transform Word documents with the SuperDoc CLI v1 operation surface.

When should I use DOCX Processing Superdoc?

DOCX Processing Superdoc fits situations like: the user asks to read; review changes in .docx files.

How do I install DOCX Processing Superdoc in Claude Code?

Run `npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a claude-code`. Or copy the skill folder (skills/word-editor-superdoc in lawve-ai/awesome-legal-skills) into .claude/skills/docx-processing-superdoc in your project. Claude Code loads it when a task matches its description.

How do I install DOCX Processing Superdoc in Codex?

Run `npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a codex`. Or copy the skill folder (skills/word-editor-superdoc in lawve-ai/awesome-legal-skills) into .agents/skills/docx-processing-superdoc in your project. Codex loads it when a task matches its description.

Can I use DOCX Processing Superdoc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lawve-ai/awesome-legal-skills --skill docx-processing-superdoc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docx-processing-superdoc, .gemini/skills/docx-processing-superdoc, .github/skills/docx-processing-superdoc and .opencode/skills/docx-processing-superdoc in your project.

What does DOCX Processing Superdoc need to run?

Going by SKILL.md and its folder, DOCX Processing Superdoc needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does DOCX Processing Superdoc access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is DOCX Processing Superdoc safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does DOCX Processing Superdoc use?

DOCX Processing Superdoc is published under the AGPL-3.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does DOCX Processing Superdoc use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to DOCX Processing Superdoc?

Skills that share tags, products or a category with DOCX Processing Superdoc: Markitdown (ImCa0/just-laws, 781 stars), DOCX (rvdbreemen/OTGW-firmware, 207 stars), Gzh Design (isjiamu/gzh-design-skill, 3.9k stars) and Word Document Reader and Writer (HKUDS/DeepTutor, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains DOCX Processing Superdoc?

lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 836 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.

Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install DOCX Processing Superdoc

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SuperDoc CLI (v1)

First Step: Discover Exact Params

Preferred Workflows

1) Stateful multi-step edits (recommended)

2) Stateless one-off reads

3) Stateless one-off mutations

Safety: preview before apply

Common v1 Commands

Query & inspect

Mutate

Format

Lists

Comments

Track changes

History

Low-level

JSON/File Payload Flags

Output and Global Flags

Legacy Compatibility (Use Sparingly)

Files

Compare with similar skills

Similar skills

More from lawve-ai/awesome-legal-skills

Related

Questions about DOCX Processing Superdoc