/review-contract - Contract Review
MCP connectors
None required. This skill operates on local repo files only.
Review a contract against standard positions. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.
Important: This assists with legal workflows but does not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
Invocation
/review-contract <contract file or URL>
Workflow
Step 1: Accept the Contract
Accept in any format: PDF, DOCX, pasted text, or file path.
If no contract is provided, prompt the user.
Step 2: Gather Context
Ask:
- Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner)
- Deadline: When does this need to be finalized?
- Focus areas: Any specific concerns?
- Deal context: Deal size, strategic importance, existing relationship?
Proceed with partial context if needed, noting assumptions.
Step 3: Load Standard Positions
Load standard contract positions from legal/templates/enterprise-service-agreement.md.
If no template exists, proceed with generic review using widely-accepted SaaS commercial standards as baseline. Note clearly.
Step 4: Clause-by-Clause Analysis
- Identify the contract type (SaaS, services, license, partnership, procurement)
- Determine the user's side
- Read the entire contract before flagging issues - clauses interact
- Analyze each material clause against standard positions
- Consider the contract holistically
Cover at minimum:
| Clause Category |
Key Review Points |
| Limitation of Liability |
Cap amount, carveouts, mutual vs. unilateral, consequential damages |
| Indemnification |
Scope, mutual vs. unilateral, cap, IP infringement, data breach |
| IP Ownership |
Pre-existing IP, developed IP, open source, license grants |
| Data Protection |
DPA, processing terms, self-hosted vs. cloud, sub-processors, breach notification |
| Confidentiality |
Scope, term, carveouts, return/destruction |
| Warranties |
Scope, disclaimers, survival period |
| Term & Termination |
Duration, renewal, termination for convenience/cause, wind-down |
| Governing Law |
Jurisdiction, venue, arbitration vs. litigation |
| Payment Terms |
Net terms, late fees, taxes, price escalation |
| SLA & Support |
Uptime, response times, support channels |
Step 5: Flag Deviations
GREEN - Acceptable
Aligns with or better than standard position. No action needed.
YELLOW - Negotiate
Outside standard position but within negotiable range. Generate redlines.
RED - Escalate
Outside acceptable range, poses material risk. Requires escalation.
Step 6: Generate Redlines
For each YELLOW and RED deviation:
**Clause**: [Section reference]
**Current language**: "[quote]"
**Proposed redline**: "[alternative language]"
**Rationale**: [1-2 sentences, suitable for external sharing]
**Priority**: [Must-have / Should-have / Nice-to-have]
**Fallback**: [Alternative position if rejected]
Step 7: Business Impact Summary
- Overall risk assessment: High-level view
- Top 3 issues: Most important items to address
- Negotiation strategy: Which issues to lead with, what to concede
- Timeline considerations: Urgency factors
Notes
- For non-English contracts, ask if the user wants translation or review in the original language
- For long contracts (50+ pages), focus on material sections first
- Always remind that analysis should be reviewed by qualified legal counsel
Self-improvement
After the CAO (or legal counsel) reviews the contract analysis:
- If they override a risk assessment (e.g. marked something RED that should have been YELLOW, or vice versa), update the risk calibration in this skill
- If they flag a clause type or risk pattern not covered in the Clause-by-Clause table, add it
- Update
legal/_insights.md with the correction and the reasoning
- If new standard positions emerge from negotiations (e.g. "we now accept mutual liability caps at 2x annual fees"), update
legal/templates/enterprise-service-agreement.md
- If a review format or negotiation strategy worked well, save it to
legal/_examples/ as a reference
1---2name: review-contract3description: Review a contract against standard negotiation positions - flag deviations, generate redlines, provide business impact analysis. Use when reviewing vendor or customer agreements, when you need clause-by-clause analysis, or when preparing a negotiation strategy.4---56# /review-contract - Contract Review78## MCP connectors910None required. This skill operates on local repo files only.1112Review a contract against standard positions. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.1314**Important**: This assists with legal workflows but does not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.1516## Invocation1718```19/review-contract <contract file or URL>20```2122## Workflow2324### Step 1: Accept the Contract2526Accept in any format: PDF, DOCX, pasted text, or file path.27If no contract is provided, prompt the user.2829### Step 2: Gather Context3031Ask:321. **Which side are you on?** (vendor/supplier, customer/buyer, licensor, licensee, partner)332. **Deadline**: When does this need to be finalized?343. **Focus areas**: Any specific concerns?354. **Deal context**: Deal size, strategic importance, existing relationship?3637Proceed with partial context if needed, noting assumptions.3839### Step 3: Load Standard Positions4041Load standard contract positions from `legal/templates/enterprise-service-agreement.md`.4243If no template exists, proceed with generic review using widely-accepted SaaS commercial standards as baseline. Note clearly.4445### Step 4: Clause-by-Clause Analysis46471. Identify the contract type (SaaS, services, license, partnership, procurement)482. Determine the user's side493. Read the entire contract before flagging issues - clauses interact504. Analyze each material clause against standard positions515. Consider the contract holistically5253Cover at minimum:5455| Clause Category | Key Review Points |56|----------------|-------------------|57| **Limitation of Liability** | Cap amount, carveouts, mutual vs. unilateral, consequential damages |58| **Indemnification** | Scope, mutual vs. unilateral, cap, IP infringement, data breach |59| **IP Ownership** | Pre-existing IP, developed IP, open source, license grants |60| **Data Protection** | DPA, processing terms, self-hosted vs. cloud, sub-processors, breach notification |61| **Confidentiality** | Scope, term, carveouts, return/destruction |62| **Warranties** | Scope, disclaimers, survival period |63| **Term & Termination** | Duration, renewal, termination for convenience/cause, wind-down |64| **Governing Law** | Jurisdiction, venue, arbitration vs. litigation |65| **Payment Terms** | Net terms, late fees, taxes, price escalation |66| **SLA & Support** | Uptime, response times, support channels |6768### Step 5: Flag Deviations6970#### GREEN - Acceptable71Aligns with or better than standard position. No action needed.7273#### YELLOW - Negotiate74Outside standard position but within negotiable range. Generate redlines.7576#### RED - Escalate77Outside acceptable range, poses material risk. Requires escalation.7879### Step 6: Generate Redlines8081For each YELLOW and RED deviation:8283```84**Clause**: [Section reference]85**Current language**: "[quote]"86**Proposed redline**: "[alternative language]"87**Rationale**: [1-2 sentences, suitable for external sharing]88**Priority**: [Must-have / Should-have / Nice-to-have]89**Fallback**: [Alternative position if rejected]90```9192### Step 7: Business Impact Summary9394- **Overall risk assessment**: High-level view95- **Top 3 issues**: Most important items to address96- **Negotiation strategy**: Which issues to lead with, what to concede97- **Timeline considerations**: Urgency factors9899## Notes100101- For non-English contracts, ask if the user wants translation or review in the original language102- For long contracts (50+ pages), focus on material sections first103- Always remind that analysis should be reviewed by qualified legal counsel104105## Self-improvement106107After the CAO (or legal counsel) reviews the contract analysis:1081091. If they override a risk assessment (e.g. marked something RED that should have been YELLOW, or vice versa), update the risk calibration in this skill1102. If they flag a clause type or risk pattern not covered in the Clause-by-Clause table, add it1113. Update `legal/_insights.md` with the correction and the reasoning1124. If new standard positions emerge from negotiations (e.g. "we now accept mutual liability caps at 2x annual fees"), update `legal/templates/enterprise-service-agreement.md`1135. If a review format or negotiation strategy worked well, save it to `legal/_examples/` as a reference
getnao