evolsb

Contract Review Skill — Development skill for Claude Code

Development community intermediate

Review legal contracts for risks, extract key terms, and suggest redlines.

How to install Contract Review Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open evolsb/claude-legal-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Contract Review Skill does

Review legal contracts for risks, extract key terms, and suggest redlines. Built on the CUAD dataset (41 risk categories), ContractEval benchmarks, and LegalBench.

Alternatives in Development

Identify Assumptions New — Identify risky assumptions for new products across 8 risk categories 7.8k ★
Sanitize — Detect and redact PII from text files — 15 categories (SSNs, credit cards, API keys, etc.), zero dependencies 3.1k ★
Add Dataset — Renamed → /portaljs-add-dataset 2.3k ★

README

name: contract-review description: Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents. Identifies unfavorable terms, suggests redlines, and compares to market standards. Use for contract analysis, due diligence, or negotiation prep. version: 3.0.0

Contract Review Skill

Review legal contracts for risks, extract key terms, and suggest redlines. Built on the CUAD dataset (41 risk categories), ContractEval benchmarks, and LegalBench.

When to Activate

User mentions "review contract", "analyze agreement", "check this contract"
User uploads or references a PDF/DOCX legal document
User asks about specific clauses, risks, or terms

Step 1: Pre-Review Checklist

Before analyzing content, verify document completeness:

Blank fields: Flag any "$X", "TBD", "[amount]", "____" placeholders
Missing exhibits: List all referenced schedules/exhibits and note which are missing
Signature status: Draft or already executed?
All pages present: Check for truncation or missing sections

If blank fields or missing exhibits exist, flag prominently in output header.

Step 2: Identify Document Type & User Position

**Ask if unclear:** "Which party are you? (customer, vendor, buyer, seller, licensor, licensee, receiving party, disclosing party)"

This affects what's "risky":

Customer reviewing vendor agreement → flag vendor-favorable terms
Vendor reviewing own template → flag customer-favorable terms
Buyer in M&A → flag seller-favorable terms
Seller in M&A → flag buyer-favorable terms
Receiving party in NDA → flag disclosing party-favorable terms

**Assess power dynamic:**

Startup vs. large enterprise? (limited negotiating leverage)
Standard form vs. negotiated? (some terms non-negotiable)
Regulated industry? (some terms legally required)

Output Format

Use **markdown** for readable, scannable output. Do NOT use XML tags.

Example Output

# Contract Review: [Document Name]

**Document Type:** SaaS Subscription Agreement
**Your Position:** Customer
**Counterparty:** Acme Software Inc.
**Risk Level:** 🟡 Medium
**Document Status:** Draft / Executed on [date]

## ⚠️ Pre-Signing Alerts

- **Blank field:** Fee amount in Section 4.1 is "$____"
- **Missing exhibit:** Exhibit B (SLA) referenced but not attached

## Executive Summary

Standard vendor agreement with some one-sided terms. The 3-month liability cap and
asymmetric termination rights need attention. Data ownership is clear.

---

## Key Terms

| Term | Value | Location |
|------|-------|----------|
| Initial Term | 12 months | Section 8.1 |
| Auto-Renewal | 12-month periods, 60-day notice | Section 8.2 |
| Liability Cap | 3 months' fees | Section 10.2 |
| Governing Law | Delaware | Section 12.1 |

---

## Red Flags (Quick Scan)

| Flag | Found | Location |
|------|-------|----------|
| Liability cap < 6 months | ⚠️ Yes | Section 10.2 |
| Uncapped indemnification | No |