Review Contract
Compare vendor or customer contracts clause-by-clause to your negotiation playbook and produce prioritized redlines and business impact notes before you sign.
Overview
review-contract is an agent skill most often used in Validate (also Operate, Grow) that reviews agreements against a negotiation playbook with deviations, redlines, and business impact analysis.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill review-contractWhat is this skill?
- Accepts PDF, DOCX, URL, or pasted text then maps clauses to your organization's playbook positions
- Flags deviations, suggests redlines, and summarizes business impact for negotiation prep
- Structured /review-contract invocation with argument-hint for contract file or text
- Explicit disclaimer: assists legal workflows; qualified counsel must review before reliance
Adoption & trust: 1.8k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a dense vendor or customer contract but no structured way to compare it to your standard terms before committing spend or liability.
Who is it for?
Founders with a defined playbook who need fast, repeatable first-pass contract review on uploads or CLM links before counsel or counterparty calls.
Skip if: Substitute for professional legal advice, jurisdictions you have no playbook for, or informal handshake deals with no written agreement.
When should I use this skill?
Reviewing vendor or customer agreements when you need clause-by-clause analysis against standard positions or a negotiation strategy with prioritized redlines.
What do I get? / Deliverables
You get clause-level deviation flags, suggested redlines, and prioritized negotiation notes aligned to your playbook for human legal review.
- Clause-by-clause deviation report vs playbook
- Redline suggestions and prioritized fallback positions
- Business impact summary for negotiation (not legal opinion)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate is where solo founders decide whether commercial terms are acceptable before money and liability lock in—contracts are the artifact. Pricing subphase captures subscription, liability, renewal, and fee clauses that determine whether a deal fits your unit economics.
Where it fits
Compare a cloud vendor's auto-renew and liability caps to your playbook before approving annual prepay.
Re-run review on a renewal draft that slipped in new data-processing or indemnity language.
Draft redlines on a first enterprise customer MSA while preserving your standard limitation-of-liability floor.
How it compares
Playbook-driven clause review skill—not a CLM product or automated e-signature platform.
Common Questions / FAQ
Who is review-contract for?
Solo SaaS operators and small teams who maintain negotiation standards and want agent-assisted first-pass review on real agreement files.
When should I use review-contract?
In Validate before signing vendor or customer deals; in Operate for renewals; and in Grow when partnership or enterprise contracts need redline prep against your playbook.
Is review-contract safe to install?
Treat uploaded contracts as sensitive; the skill processes document content in-agent—review the Security Audits panel on this page and your connector permissions in CONNECTORS.md.
SKILL.md
READMESKILL.md - Review Contract
# /review-contract -- Contract Review Against Playbook > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Review a contract against your organization's negotiation playbook. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis. **Important**: You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon. ## Invocation ``` /review-contract <contract file or URL> ``` Review the contract: @$1 ## Workflow ### Step 1: Accept the Contract Accept the contract in any of these formats: - **File upload**: PDF, DOCX, or other document format - **URL**: Link to a contract in your CLM, cloud storage (e.g., Box, Egnyte, SharePoint), or other document system - **Pasted text**: Contract text pasted directly into the conversation If no contract is provided, prompt the user to supply one. ### Step 2: Gather Context Ask the user for context before beginning the review: 1. **Which side are you on?** (vendor/supplier, customer/buyer, licensor, licensee, partner -- or other) 2. **Deadline**: When does this need to be finalized? (Affects prioritization of issues) 3. **Focus areas**: Any specific concerns? (e.g., "data protection is critical", "we need flexibility on term", "IP ownership is the key issue") 4. **Deal context**: Any relevant business context? (e.g., deal size, strategic importance, existing relationship) If the user provides partial context, proceed with what you have and note assumptions. ### Step 3: Load the Playbook Look for the organization's contract review playbook in local settings (e.g., `legal.local.md` or similar configuration files). The playbook should define: - **Standard positions**: The organization's preferred terms for each major clause type - **Acceptable ranges**: Terms that can be agreed to without escalation - **Escalation triggers**: Terms that require senior counsel review or outside counsel involvement **If no playbook is configured:** - Inform the user that no playbook was found - Offer two options: 1. Help the user set up their playbook (walk through defining positions for key clauses) 2. Proceed with a generic review using widely-accepted commercial standards as the baseline - If proceeding generically, clearly note that the review is based on general commercial standards, not the organization's specific positions ### Step 4: Clause-by-Clause Analysis Apply the following review process: 1. **Identify the contract type**: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material. 2. **Determine the user's side**: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties). 3. **Read the entire contract** before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability). 4. **Analyze each material clause** against the playbook position. 5. **Consider the contract holistically**: Are the overall risk allocation and commercial terms balanced? Analyze the contract systematically, covering at minimum: | Clause Category | Key Review Points | |----------------|-------------------| | **Limitation of Liability** | Cap amount, carveouts, mutual vs. unilateral, consequential damages | | **Indemnification*