Legal Drafting (Contract Review)

Reviewed 2026-10-23writingPrompt / Rule# legal # contracts # redlines # contract-review # legal-drafting

Anthropic's review-contract skill: check a contract against your playbook, flag GREEN/YELLOW/RED clauses and draft ready-to-insert redlines.

Security Reviewed

Low risk: a single Markdown file with no scripts; the main concern is confidentiality of the contracts you share and the need for lawyer review.

Install Legal Drafting (Contract Review) in Google Antigravity

Antigravity loads skills from .agents/skills/ in your project or ~/.gemini/config/skills/ for all projects (official docs). Full guide

EasiestOption 1: paste this to your Antigravity agent

Install the "Legal Drafting (Contract Review)" skill for Google Antigravity.
Follow the steps at https://www.antigravityskills.org/install/legal-drafting.md (source: https://github.com/anthropics/knowledge-work-plugins/tree/main/legal/skills/review-contract).
Before running anything, show me what you will download and whether it includes scripts, and wait for my OK.
Install it into this project (.agents/skills/) unless I say global. When done, check that Antigravity lists it as an installed skill.

The agent reads the install file, shows you what it will download and waits for your OK.

Option 2: install it yourself

1. Clone the source repository
```
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins /tmp/kwp
```
Clone the repository to a temporary folder so you can copy the skill folder out of it.

2. Copy into your workspace (this project only)

mkdir -p .agents/skills && cp -r /tmp/kwp/legal/skills/review-contract .agents/skills/review-contract && cp -r /tmp/kwp/legal/skills/legal-response .agents/skills/legal-response

Run this from your project root. Antigravity reads workspace skills from <project>/.agents/skills/<folder>/.

3. Or copy globally (all projects)

mkdir -p ~/.gemini/config/skills && cp -r /tmp/kwp/legal/skills/review-contract ~/.gemini/config/skills/review-contract && cp -r /tmp/kwp/legal/skills/legal-response ~/.gemini/config/skills/legal-response

Use this instead of the workspace step if you want the skill available in every project. Antigravity reads global skills from ~/.gemini/config/skills/<folder>/.

4. Check that Antigravity sees it
Start a new agent session and ask "What skills do you have?" (in the Antigravity CLI you can also run /skills). The skill name from the SKILL.md frontmatter (review-contract) should appear.

No API keys needed. The legal README does not mention Antigravity; this is a plain folder copy. Put your playbook in a legal.local.md file in the project so the skill can find it, and name the contract file in your prompt (the SKILL.md's @$1 placeholder is a Claude Code feature). legal-response (templated replies) is optional; add triage-nda or legal-risk-assessment from the same folder if useful.

Using Claude Code, Cursor or Codex? See other assistants below.

What is Legal Drafting (Contract Review)?

Legal Drafting here is Anthropic's review-contract skill, for in-house lawyers and small teams who must check a vendor or customer contract against their own negotiation positions: it reads the contract clause by clause, labels each deviation GREEN, YELLOW or RED, and writes ready-to-insert redline text with a fallback. What we counted at commit 33d3dea (HEAD on 2026-10-23; the legal/ folder is identical to the 8444efc we first reviewed): review-contract is one SKILL.md of 358 lines and 16,708 bytes with no scripts, no shell commands and no URLs; it checks 12 clause categories in a table, gives detailed guidance for 6 of them (liability, indemnification, IP, data protection, term and termination, governing law), and each redline has 5 fields (current language, proposed redline, rationale, priority, fallback). The legal plugin around it has 9 skill folders and 14 tracked files. The README says the default playbook examples reflect U.S. positions (Delaware, New York, California). It reviews an existing contract; it does not write one from scratch, and unlike the general writing pages on this site (technical-writing, grant-writing) it is built around a playbook file you supply.

How to use Legal Drafting (Contract Review)?

Optionally write a legal.local.md playbook with your standard positions, acceptable ranges and escalation triggers (the README shows a template; Claude Code keeps it in .claude/). Then give the agent the contract as a file, URL or pasted text and say which side you are on. The SKILL.md has the agent ask for your side, deadline, focus areas and deal context first, then review. If no playbook is found it says so and offers to help you build one or to review against general commercial standards, clearly labelled as such. The SKILL.md ends its invocation with the Claude Code placeholder @$1; in other agents, name the contract file or paste the text in your prompt instead.

Key features of Legal Drafting (Contract Review)

✓Clause-by-clause review across 12 categories, from liability and indemnification to insurance, assignment, force majeure and payment terms
✓GREEN / YELLOW / RED classification of each deviation from your playbook
✓Redlines with current language, proposed language, rationale, priority and fallback position
✓Three negotiation tiers (must-have, should-have, nice-to-have) and a business impact summary
✓Generic-standards fallback when no playbook exists, labelled as generic
✓Optional CLM routing step, skipped when no contract lifecycle system is connected

When to use Legal Drafting (Contract Review)

1Review a vendor SaaS agreement before signing
2Draft redlines for a customer contract
3Prepare a negotiation strategy with fallback positions
4Check data protection and DPA terms
5Spot uncapped liability or broad IP assignment

Installation & Setup Guide

Agent Rules / Prompt Setup

Follow these steps (taken from the project's own docs) to configure Legal Drafting (Contract Review) in your development environment.

Step 1: Add the marketplace (Claude Code)claude

claude plugin marketplace add anthropics/knowledge-work-plugins

Documented in legal/README.md, Installation.

Step 2: Install the legal plugin (Claude Code)claude

claude plugin install legal@knowledge-work-plugins

Then save your playbook as .claude/legal.local.md in your project and run /review-contract (README, Quick Start). The README says the plugin is primarily designed for Cowork and also works in Claude Code.

Step 3: Cursor: not documentedcursor

Neither the legal README nor the repository README mentions Cursor, so we do not list a Cursor command.

Usage Example & Verification

Prompt / Request Example

1) README example (legal/README.md, Contract Review workflow): run /review-contract, upload the contract and answer with context such as "We are the customer, need to close by end of quarter, focus on data protection and liability".
-> What happens: the agent reviews clause by clause and returns GREEN/YELLOW/RED flags with redline language for the YELLOW and RED items.

2) Our example: "Review contracts/acme-msa.docx as the vendor, using the playbook in legal.local.md. Focus on the liability cap and indemnification."
-> What happens: the SKILL.md steps load the playbook, compare the liability and indemnification clauses with your standard and escalation triggers, and write redlines in the 5-field format.

3) Our example: "Review this SaaS agreement as the customer. I do not have a playbook yet."
-> What happens: per Step 3 of the SKILL.md the agent tells you no playbook was found and offers either to help you define positions or to proceed with a generic review labelled as based on general commercial standards.

Installation Confirmation Method

Start a new session and ask "What skills do you have?" (Antigravity CLI: /skills); review-contract should be listed. Then paste a short sample clause and ask for a review: the agent should ask which side you are on before it answers.

Security Review

Static review

Reviewed Date

2026-10-23

Audited Ref / Commit

33d3dea41a341b341d4f5da2e8801ae0c89be2b8

Reviewer

antigravityskills.org (static code review)

Low risk: a single Markdown file with no scripts; the main concern is confidentiality of the contracts you share and the need for lawyer review.

Full review: scope, findings, risks

Audit Scope:Static review at commit 33d3dea (2026-10-21, HEAD on 2026-10-23); git diff against the earlier review at 8444efc shows no change under legal/. Files read: legal/skills/review-contract/SKILL.md (full), the frontmatter of the other 8 legal skills, legal/README.md, legal/.mcp.json, legal/.claude-plugin/plugin.json, legal/LICENSE and the repository README.md. Grepped review-contract and legal-response for shell code blocks and URLs.

Key Findings:Markdown-only skill: review-contract/SKILL.md (358 lines) has no shell code blocks, no scripts and no URLs. It reads the supplied contract (file, URL or pasted text) and a local legal.local.md playbook, and in Step 8 may route to a connected CLM system. The plugin's .mcp.json declares 7 entries: remote HTTP MCP servers for Slack, Box, Egnyte, Atlassian and DocuSign, plus empty Google Calendar and Gmail URLs; none connect unless you sign in. Copying only the skill folder does not install them.

Identified Operational Risks & Permissions:Confidential contracts are processed by the AI model and may be fetched from connected document systems; the output is not legal advice and the default playbook assumes U.S. law. Static review only: we did not run the skill.

Static review at commit 33d3dea (legal/ identical to 8444efc). legal/skills/review-contract/SKILL.md is the only file in the skill folder and contains no shell code blocks, no scripts and no URLs. It accepts a contract as a file, URL or pasted text and looks for a local playbook such as legal.local.md. Step 8 suggests CLM routing only if a contract lifecycle system is connected via MCP. legal/.mcp.json lists remote MCP servers for Slack (mcp.slack.com), Box (mcp.box.com), Egnyte, Atlassian and DocuSign that need your own sign-in, plus empty Google Calendar and Gmail entries. legal/.claude-plugin/plugin.json (version 1.3.0, author Anthropic) declares no hooks or commands. SKILL.md and legal/README.md both state the tool does not provide legal advice and that results must be reviewed by qualified legal professionals.

Operational Notes & Known Limitations

Known Limitations

•Not legal advice: the plugin README and the SKILL.md both say output must be reviewed by licensed attorneys
•Default playbook examples reflect U.S. positions (Delaware, New York, California); other jurisdictions must customise legal.local.md (README)
•It reviews and redlines an existing contract; it does not draft a full contract from scratch
•Written for Cowork and Claude Code: the SKILL.md uses the @$1 argument placeholder and the README's skills table names four skills (contract-review, nda-triage, compliance, canned-responses) that are not folder names in the repo (the folders are review-contract, triage-nda, compliance-check and legal-response, we counted)
•Reading contracts from Box, Egnyte, Slack or DocuSign needs the plugin's MCP connectors and your own accounts; none of that is installed when you copy only the skill folder

Frequently Asked Questions

Is the Contract Review skill safe?

In our static review of commit 33d3dea, review-contract is one Markdown file with no scripts, shell commands or URLs. It reads the contract you supply and your local legal.local.md playbook. The legal plugin's .mcp.json lists 7 entries (Slack, Box, Egnyte, Atlassian, DocuSign, plus empty Google Calendar and Gmail) that only connect if you authorise them. The real risk is confidentiality: your contract goes to the AI model. Treat the output as a draft for a lawyer.

How do I install review-contract in Antigravity?

Clone https://github.com/anthropics/knowledge-work-plugins and copy legal/skills/review-contract into .agents/skills/ (project) or ~/.gemini/config/skills/ (global), then ask "What skills do you have?" (Antigravity CLI: /skills). The legal README does not mention Antigravity, so this follows Antigravity's standard skill folders. Add a legal.local.md playbook to your project.

Can it write a contract from scratch?

No. It reviews an existing contract and drafts redline language for problem clauses. The sibling legal-response skill drafts templated replies to common legal inquiries.

What if I have no playbook, or I am outside the U.S.?

Without a playbook the skill offers to help you define positions or to run a generic review labelled as such. The README warns that its default examples reflect U.S. law and must be customised for the EU, UK and other systems.

Does it work in Claude Code or Cursor?

Claude Code: yes, install the legal plugin from the marketplace (README). Cursor: the project does not document it. The same plugin also ships 8 other legal skills such as triage-nda and compliance-check.

Supported Platforms

antigravityclaudecodex

View Source on GitHub

Keep exploring this topic

Browse the full Antigravity skills directory for more source-linked skills with install steps and static safety reviews.

More writing skills #legal #contracts #redlines #contract-review Use cases

Related Skills

✍️

Grant Writing

@K-Dense-AI

K-Dense's research-grants skill: helps researchers plan, check and critique NSF, NIH, DOE, DARPA and Taiwan NSTC proposals against the actual call.

Static reviewinstructions onlynetwork accesswrites files

grant-writingresearch-proposals

✍️

Technical Writing

@anthropics

Anthropic's doc-coauthoring skill: a three-stage workflow in which the agent interviews you, drafts a spec or design doc section by section, then tests it on a fresh reader.

Static reviewwrites filesinstructions only

technical-writingdocumentation

💻

Cursor Code Review (Superpowers)

@obra

Superpowers' requesting-code-review skill: the agent sends a git diff to a reviewer subagent and gets Critical/Important/Minor findings and a verdict.

Static reviewruns scriptsoffline

code-reviewcursor