Word Editor
Edit, query, and transform Word documents (.docx) with the SuperDoc CLI. Use when the user asks to read, search, modify, format, comment, track changes, or review changes in .docx files. Triggers on any task involving Word documents — text replacement, redlining, contract markup, template filling, bulk edits, content extraction, or document review.
npx skills add lawve-ai/awesome-legal-skills --skill word-editor-antoine-louis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## Auto-Open in VS Code Before starting any edit workflow, check if running inside VS Code by testing `VSCODE_PID`. If set, open the target document so the user sees changes live: ```bash if [ -n "$VSCODE_PID" ]; then for cmd in code code-insiders cursor; do if command -v "$cmd" > /dev/null 2>&1; then "$cmd" "$DOC_PATH"; break; fi done fi ``` - `VSCODE_PID` is set by VS Code itself — works for any agent extension (Claude Code, Codex, Cline, etc.) and the integrated terminal. - Skip silently if not set. Idempotent: re-opening focuses the existing tab. ## Edit Identity: Ask Before Starting Before opening a document for editing, ask the user under which name tracked changes should be attributed: 1. Their own name (e.g., the lawyer reviewing the document) 2. The AI agent's name as default (e.g., "Claude", "Codex", "Gemini") Use the chosen name in `--user-name` on `open`. Convention for email: `<name>@lawvab
- Auto-Open in VS Code
- Edit Identity: Ask Before Starting
- Default Edit Mode: Tracked Changes
- Save After Every Mutation
- Command Reference
- Common Patterns
- Global find & replace (most common)
- Targeted single edit
- Tight group of related mutations
- Stateless reads (no session needed)
- Stateless mutation
- Safety
- Important Notes
if [ -n "$VSCODE_PID" ]; then
for cmd in code code-insiders cursor; do
if command -v "$cmd" > /dev/null 2>&1; then "$cmd" "$DOC_PATH"; break; fi
done
fi
superdoc open ./contract.docx --user-name "Claude" --user-email "claude@lawvable.com"
superdoc mutations apply --atomic true --change-mode tracked --steps-json '[
superdoc save
superdoc close
superdoc query match --select-json '{"type":"text","pattern":"termination"}' --require exactlyOneWhat does the Word Editor skill do?
Edit, query, and transform Word documents (.docx) with the SuperDoc CLI. Use when the user asks to read, search, modify, format, comment, track changes, or review changes in .docx files. Triggers on any task involving Word documents — text replacement, redlining, contract markup, template filling, bulk edits, content extraction, or document review.
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill word-editor-antoine-louis --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.
