edit-docx-agreementlisted

Make bespoke edits to a DOCX agreement generated by OpenAgreements (or any existing DOCX), using Safe Docx MCP tools for surgical, formatting-preserving edits and tracked-changes outputs. Use when user says "edit this contract," "change a clause," "modify the agreement," "custom edits to the docx," or "bespoke changes to the document."
open-agreements/open-agreements · ★ 34 · Data & Documents · score 81

Install: claude install-skill open-agreements/open-agreements

# edit-docx-agreement Use this skill when a user asks for **custom edits that are not exposed as template fields** in an OpenAgreements-generated (or any existing) DOCX agreement. > **Interactivity note**: Always ask the user for missing inputs (file path, change intent, output preferences). ## Security model This skill bridges two separate systems: - **OpenAgreements** (remote MCP or local CLI) — for template filling. Follows the OpenAgreements zero-download security model. - **Safe Docx** (local MCP server) — for surgical DOCX editing. Requires separate setup. This is **not** part of the OpenAgreements skill set and has its own trust/security model. The agent must have Safe Docx MCP tools available to perform edits. If Safe Docx tools are not detected, inform the user and provide setup guidance (see Connectors). ## Decision rule: refill vs edit vs both 1. **Field-only changes** (e.g., party name, date, amount, valuation cap): Re-run OpenAgreements `fill_template` with the updated field values. No Safe Docx needed. 2. **Boilerplate-only changes** (e.g., custom clause, modified standard language): Use Safe Docx MCP tools to surgically edit the existing DOCX. 3. **Mixed changes** (field updates + bespoke edits): Re-fill via OpenAgreements first (to get a clean base with updated fields), save the output locally, then use Safe Docx to apply bespoke edits on the fresh file. ## Execution ### Step 0: Confirm you have a local .docx file path - If OpenAgreements