FISCFED9/CLI / .agents/skills/docx-processing-lawvable
Word Editor
VerifiedEdit, 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.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 33.7 KB |
| SKILL.md | skill md | 5.6 KB |
| references/bookmarks-footnotes.md | markdown | 2.2 KB |
| references/citations.md | markdown | 2.6 KB |
| references/comments.md | markdown | 2.6 KB |
| references/content-controls.md | markdown | 6.2 KB |
| references/create.md | markdown | 2.6 KB |
| references/diff.md | markdown | 2.0 KB |
| references/format.md | markdown | 7.3 KB |
| references/headers-footers.md | markdown | 1.4 KB |
| references/hyperlinks.md | markdown | 2.1 KB |
| references/images.md | markdown | 2.6 KB |
| references/index.md | markdown | 6.0 KB |
| references/lists.md | markdown | 4.3 KB |
| references/mutations-apply.md | markdown | 6.4 KB |
| references/mutations.md | markdown | 4.8 KB |
| references/protection.md | markdown | 849 B |
| references/reading.md | markdown | 5.2 KB |
| references/sections.md | markdown | 1.8 KB |
| references/session.md | markdown | 2.7 KB |
| references/tables.md | markdown | 7.2 KB |
| references/toc.md | markdown | 2.3 KB |
| references/track-changes.md | markdown | 1.8 KB |
SKILL.md
View on GitHub---
name: "Word Editor"
description: "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."
metadata:
author: "Dr. Antoine Louis"
license: "agpl-3.0"
version: "2026-04-10"
---
# 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>@lawvable.com`.
## Default Edit Mode: Tracked Changes
**Always use `--tracked` on every mutating command** unless the user explicitly asks for direct edits.
- `--tracked` is shorthand for `--change-mode tracked`.
- If a command returns `TRACK_CHANGE_COMMAND_UNAVAILABLE`, fall back to direct edit for that command only.
## Save After Every Mutation
The CLI and the VS Code SuperDoc extension run separate engines — the only sync point is the file on disk.
**Call `superdoc save` after every mutation** so changes appear live.
- Single mutation → `save` immediately.
- Tight group of 2-3 related mutations (e.g., replace + format) → `save` once after the group.
- Never defer `save` to end of session.
## Command Reference
**Read [references/index.md](references/index.md)** first — it lists all reference files by topic. Then read only the relevant file for your task (e.g., `references/track-changes.md` for accepting/rejecting changes, `references/mutations-apply.md` for batch find-and-replace).
Do NOT read all reference files at once — pick only what you need.
For commands not covered in any reference file, use `superdoc describe command "<name>"` as fallback.
## Common Patterns
### Global find & replace (most common)
Use `mutations apply` with `text.rewrite` + `require: "all"`. **Do NOT manually find → parse → build steps.**
```bash
superdoc open ./contract.docx --user-name "Claude" --user-email "claude@lawvable.com"
superdoc mutations apply --atomic true --change-mode tracked --steps-json '[
{"id":"s1","op":"text.rewrite",
"where":{"by":"select","select":{"type":"text","pattern":"Lawvable"},"require":"all"},
"args":{"replacement":{"text":"Google"}}}
]'
superdoc save
superdoc close
```
- `require: "all"` → every match. `"first"` → first only. `"exactlyOne"` → fails if != 1.
- Batch multiple replacements in the same `steps` array (see [references/commands.md](references/commands.md)).
### Targeted single edit
Use `query match` (not `find`) to locate a target, then `replace`:
```bash
superdoc open ./contract.docx --user-name "Claude" --user-email "claude@lawvable.com"
superdoc query match --select-json '{"type":"text","pattern":"termination"}' --require exactlyOne
superdoc replace --tracked --target-json '{"kind":"text","blockId":"p1","range":{"start":0,"end":11}}' --text "expiration"
superdoc save
superdoc close
```
- `query match` returns exact addresses with cardinality guarantees. `find` does not — use it only for exploration.
- After `open`, commands run against the active session when `<doc>` is omitted.
### Tight group of related mutations
```bash
superdoc open ./contract.docx --user-name "Claude" --user-email "claude@lawvable.com"
superdoc query match --select-json '{"type":"text","pattern":"ACME Corp"}' --require exactlyOne
superdoc replace --tracked --target-json '{"kind":"text","blockId":"p2","range":{"start":0,"end":9}}' --text "NewCo Inc."
superdoc format bold --tracked --block-id p2 --start 0 --end 10
superdoc save
superdoc close
```
### Stateless reads (no session needed)
```bash
superdoc get-text ./proposal.docx
superdoc get-markdown ./proposal.docx
superdoc info ./proposal.docx
```
### Stateless mutation
```bash
superdoc replace --tracked ./proposal.docx \
--target-json '{"kind":"text","blockId":"p1","range":{"start":0,"end":5}}' \
--text "Updated" --out ./proposal.updated.docx
```
Stateless mutating commands require `--out` unless using `--dry-run`.
### Safety
- `--dry-run` to preview any mutation without applying.
- `--expected-revision <n>` for optimistic concurrency checks.
## Important Notes
- **Telemetry on stdout**: The CLI may print `[super-editor] Telemetry: enabled`. Use `2>/dev/null` when piping JSON. Prefer declarative selectors (`mutations apply`) over `find | parse` pipelines.
- **Legacy commands** (`search`, `replace-legacy`, `read`) exist for v0 compatibility. Use only for multi-file glob workflows.
- **Session cleanup**: `close` on dirty state requires `--discard` or a prior `save`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |