Compare two document versions and produce analysis or a Word redline. Use when the user has two versions of a document and wants to understand what changed.
Edit existing DOCX files — tracked-change redlines, placeholder fills, range deletes, comments, and accept/reject finalization. Plain-text-only tools; no raw OOXML. For structural edits beyond text replacement, invoke `Skill('docx-xml')`.
Advanced — structural OOXML edits via run_code + lxml + zipfile. Use ONLY when the docx-editing tools (edit_document, add_comment, accept/reject, revert_edit) can't express the change. For ordinary text edits, use the docx-editing skill instead.
Draft a NEW document from scratch via docx-js (run_code language="node"). Use when the user wants to create new legal content from a blank page — agreements, memos, letters, resolutions, term sheets. For filling an existing template with placeholder values, use the `docx-editing` skill instead.
Quality assurance review — 6-dimension checklist covering template compliance, factual accuracy, completeness, track changes, research audit, and instruction cross-reference.
Research a legal topic with web search and inline citations. Use when the user needs legal information, market standards, regulatory guidance, or case law references.
Review a document against playbook positions. Analyze clauses for risks, flag issues, suggest specific changes, and apply edits. Subsumes redlining — review + fix is one workflow.
Guide a first-time user through workspace initialisation. Ask about their role and work, then create a personalised folder structure, anylegal.md instructions, and a starter playbook. Use when the user says /setup, asks to set up their workspace, or the workspace appears empty and they ask where to start.