Agent skill

Contract Review

by borghei in borghei/Claude-Skills

Contract review assistant analyzing agreements against playbooks.

MITAuto-check passedLegal & Compliance

Install Contract Review

skills CLI
$ npx skills add borghei/Claude-Skills --skill contract-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills contract-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/legal/contract-review .claude/skills/contract-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
contract-review
GitHub stars
886
Token cost
~3.1k tokens
SKILL.md length
1,138 words
Files
5 (incl. scripts, references)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Contract review assistant analyzing agreements against playbooks.

  • Works in 6 steps: Ingest -- Save contract as .txt or .md… → Analyze -- Run contract_analyzer.py with… → Review findings -- Check RED items… → …
  • Reviewing vendor contracts
  • SKILL.md covers Table of Contents, Clarify First, Tools and Reference Guides, plus 6 more sections
  • Runs Python scripts from its folder; calls python

What it does

Contract Review is an agent skill from borghei/Claude-Skills. Contract review assistant analyzing agreements against playbooks. GREEN/YELLOW/RED severity. Use when reviewing vendor contracts, SaaS agreements, service agreements, or generating redline suggestions.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/clause_analysis_guide.md`, `references/negotiation_playbook.md` and `scripts/contract_analyzer.py`).

It sits in Legal & Compliance, covering Contract review. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Reviewing vendor contracts
  • SaaS agreements
  • Service agreements
  • Generating redline suggestions

Example prompts

  • “/contract-review”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Ingest -- Save contract as .txt or .md file
  2. Analyze -- Run contract_analyzer.py with --json flag
  3. Review findings -- Check RED items first, then YELLOW
  4. Generate redlines -- Run redline_generator.py on analysis output
  5. Prioritize -- Focus on Must-Have redlines, prepare fallbacks for Should-Have
  6. Send to counsel -- Attach analysis and redlines for final review

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Contract Review loads about 3.1k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 1,138 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,138 words, ~3,055 tokens.

Download SKILL.mdSave it as .claude/skills/contract-review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
contract-review
description
Contract review assistant analyzing agreements against playbooks. GREEN/YELLOW/RED severity. Use when reviewing vendor contracts, SaaS agreements, service agreements, or generating redline suggestions.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
The Glass Room
metadata.category
legal
metadata.domain
contract-analysis
metadata.updated
2026-04-10
metadata.tags
contract-review, redline, negotiation, risk-assessment, legal

⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

Contract Review

Automated contract review tools that analyze agreements against organizational playbooks, classify clause risk with GREEN/YELLOW/RED severity, and generate prioritized redline suggestions with fallback positions.


Table of Contents


Clarify First

Before reviewing the contract, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Which side you represent — customer/buyer vs vendor/provider flips which clauses are favorable and reverses the direction of every redline
  • Contract type — SaaS, services, vendor/supply, or license — sets the standard-clause baseline and which missing clauses get flagged
  • Risk tolerance / playbook positions — what your org treats as a deal-breaker — defines the RED vs YELLOW cutoff and the Must-Have vs Nice-to-Have tiering
  • Deal leverage / value — calibrates which redlines are walkaway (Tier 1) vs tradeable concessions (Tier 3)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the review.

Tools

Contract Analyzer

Analyzes contract text files for clause types, missing standard clauses, and risk indicators.

bash
# Analyze a contract file
python scripts/contract_analyzer.py contract.txt

# JSON output for pipeline integration
python scripts/contract_analyzer.py agreement.md --json

# Save analysis to file
python scripts/contract_analyzer.py contract.txt --output analysis.json --json

What it detects:

  • Clause types: Limitation of Liability, Indemnification, IP, Data Protection, Term & Termination, Governing Law, Reps & Warranties, Force Majeure, Confidentiality, Payment Terms
  • Missing standard clauses against a baseline checklist
  • Risk indicators: uncapped liability, perpetual terms, unilateral indemnification, automatic renewal without opt-out, broad IP assignment, unlimited audit rights

Risk Classification:

LevelMeaningAction
REDDeal-breaker riskMust negotiate before signing
YELLOWMaterial concernShould negotiate, may accept with mitigation
GREENStandard or favorableAcceptable as-is

Redline Generator

Takes contract analysis JSON and generates formatted redline suggestions with priority tiers.

bash
# Generate redlines from analysis
python scripts/contract_analyzer.py contract.txt --json --output analysis.json
python scripts/redline_generator.py analysis.json

# JSON output
python scripts/redline_generator.py analysis.json --json

# Save redlines to file
python scripts/redline_generator.py analysis.json --output redlines.md

Output includes:

  • Priority tier (Must-Have / Should-Have / Nice-to-Have)
  • Preferred redline language
  • Rationale for each change
  • Fallback position if counterparty rejects
  • Negotiation notes

Priority Tiers:

TierLabelDescription
1Must-HaveDeal-breakers; walk away if rejected
2Should-HaveStrong preferences; push hard but negotiable
3Nice-to-HaveConcession candidates; trade for Tier 1-2 wins

Reference Guides

Clause Analysis Guide

references/clause_analysis_guide.md

Deep reference covering 8+ clause types:

  • Limitation of Liability (cap types, carveouts, consequential damages)
  • Indemnification (mutuality, scope, procedure)
  • IP (ownership, licenses, work-for-hire, feedback)
  • Data Protection (DPA, sub-processors, breach notification, transfers)
  • Term & Termination (auto-renewal, cure periods, transition)
  • Governing Law (jurisdiction, arbitration, jury waiver)
  • Representations & Warranties
  • Force Majeure
Negotiation Playbook

references/negotiation_playbook.md

Negotiation priority framework with:

  • Tier 1 deal-breakers and walkaway criteria
  • Tier 2 strong preferences with trading strategies
  • Tier 3 concession candidates for strategic give-backs
  • Redline format template
  • Common negotiation pitfalls

Workflows

Standard Contract Review
  1. Ingest -- Save contract as .txt or .md file
  2. Analyze -- Run contract_analyzer.py with --json flag
  3. Review findings -- Check RED items first, then YELLOW
  4. Generate redlines -- Run redline_generator.py on analysis output
  5. Prioritize -- Focus on Must-Have redlines, prepare fallbacks for Should-Have
  6. Send to counsel -- Attach analysis and redlines for final review
Rapid Risk Triage
  1. Run contract_analyzer.py in text mode for quick scan
  2. If any RED findings: escalate immediately to legal counsel
  3. If YELLOW only: schedule review within 48 hours
  4. If all GREEN: proceed with standard approval workflow

Troubleshooting

ProblemCauseSolution
Error: File not foundContract file path is incorrect or file does not existVerify the file path; use absolute paths if relative paths fail
No clauses detectedContract uses unusual formatting or non-standard clause headersEnsure contract is plain text; strip PDF artifacts before analysis
All clauses marked GREENContract is genuinely favorable, or text extraction missed key sectionsManually verify critical clauses (liability, indemnification, IP) are present in the input file
Redline generator produces empty outputAnalysis JSON has no YELLOW or RED findingsConfirm analysis JSON is valid; re-run analyzer if contract was updated
False positive on uncapped liabilityLiability section references a cap elsewhere in the documentReview the full Limitation of Liability section; the tool scans for cap keywords within each clause boundary
Missing clause false positiveClause exists but uses non-standard heading (e.g., "Damages Cap" instead of "Limitation of Liability")The analyzer checks multiple heading variants; add custom aliases if your organization uses unique terminology

Show full SKILL.md (428 more words)Show less

Success Criteria

  • Contract review time reduced by 50%: Automated clause identification and risk classification eliminates manual scanning.
  • Zero missed RED-severity clauses: Every uncapped liability, unilateral indemnification, and broad IP assignment is flagged before human review.
  • Redline generation under 2 minutes: From analysis JSON to prioritized redline document.
  • Consistent risk classification across reviewers: GREEN/YELLOW/RED framework eliminates subjective assessments.
  • 100% of contracts reviewed with structured output: Every agreement gets a clause inventory and risk report before negotiation begins.
  • Negotiation success rate above 80% on Must-Have items: Tier 1 redlines with prepared fallbacks improve negotiation outcomes.

Scope & Limitations

Covers:

  • Static text analysis of contract clauses using keyword and pattern matching
  • Clause type identification across 10+ standard commercial contract categories
  • Risk indicator detection: uncapped liability, perpetual terms, unilateral obligations, auto-renewal traps
  • Missing clause detection against a standard commercial contract baseline
  • Prioritized redline generation with fallback positions

Does NOT cover:

  • Legal advice -- this tool supports review, it does not replace qualified legal counsel
  • Jurisdiction-specific compliance -- use ra-qm-team skills for regulatory compliance (GDPR, SOC 2, etc.)
  • Contract execution or e-signature workflows -- out of scope
  • Multi-document cross-reference (e.g., checking SOW against MSA) -- analyze each document separately
  • Non-English contracts -- pattern matching is English-language only

Anti-Patterns

Anti-PatternWhy It FailsBetter Approach
Signing contracts with only GREEN findings and no human reviewAutomated analysis cannot catch context-dependent risks, ambiguous language, or business-specific concernsAlways have qualified counsel review before execution, even on all-GREEN contracts
Treating all RED findings as equalSome RED items are structural deal-breakers while others may be resolvable with a single word changeUse the redline generator to assess effort and fallback positions for each RED finding
Skipping the redline fallback positionsEntering negotiation with only preferred positions leaves no room for strategic concessionAlways prepare Must-Have fallbacks and identify Nice-to-Have items to trade away
Running analysis on poorly extracted textPDF-to-text conversion artifacts break clause detection patternsClean the text file before analysis: remove headers, footers, page numbers, and formatting artifacts

Tool Reference

contract_analyzer.py

Purpose: Analyzes contract text files for clause types, identifies missing standard clauses, and flags risk indicators with GREEN/YELLOW/RED severity classification.

Usage:

bash
python scripts/contract_analyzer.py <contract_file> [--json] [--output FILE]

Flags:

FlagShortDefaultDescription
contract_file(positional)Path to contract text file (.txt or .md)
--jsonoffOutput in JSON format
--output-o(stdout)Write output to file

Example Output (JSON):

json
{
  "file": "vendor_agreement.txt",
  "clauses_found": [
    {
      "type": "limitation_of_liability",
      "severity": "RED",
      "text_snippet": "...liability shall not be limited...",
      "risk_flags": ["uncapped_liability"],
      "notes": "No liability cap found; uncapped exposure"
    }
  ],
  "missing_clauses": ["force_majeure", "data_protection"],
  "risk_summary": {"RED": 2, "YELLOW": 3, "GREEN": 5},
  "overall_risk": "RED"
}

redline_generator.py

Purpose: Takes contract analysis JSON and generates formatted redline suggestions with priority tiers, rationale, and fallback positions.

Usage:

bash
python scripts/redline_generator.py <analysis_json> [--json] [--output FILE]

Flags:

FlagShortDefaultDescription
analysis_json(positional)Path to contract analysis JSON file
--jsonoffOutput in JSON format
--output-o(stdout)Write output to file

Example Output:

REDLINE SUGGESTIONS
===================

[MUST-HAVE] Limitation of Liability — Uncapped Liability
  Severity: RED
  Preferred: "Aggregate liability shall not exceed 12 months of fees paid."
  Rationale: Uncapped liability creates unlimited financial exposure.
  Fallback: "Aggregate liability shall not exceed 24 months of fees paid."

[SHOULD-HAVE] Indemnification — Unilateral Indemnification
  Severity: YELLOW
  Preferred: "Each party shall indemnify the other for breaches of this Agreement."
  Rationale: Mutual indemnification balances risk between parties.
  Fallback: "Indemnification obligations shall be subject to the liability cap."

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in legal/contract-review of borghei/Claude-Skills.

  • SKILL.md
  • references/clause_analysis_guide.md
  • references/negotiation_playbook.md
  • scripts/contract_analyzer.py
  • scripts/redline_generator.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Contract Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Contract Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Contract Review this skillborghei/Claude-Skills886—~3.1kAutomated safety check: PassMIT
Contract Reviewevolsb/claude-legal-skill4641 repos~3.6kAutomated safety check: PassMIT
Commercial Legal Plapiotrowski-afk/commercial-legal-pl1761 repos~4.1kAutomated safety check: PassApache-2.0
Hand Drawnthreerocks/hand-drawn-styles2.2k—~398Automated safety check: PassMIT
Tabular Document Reviewanthropics/claude-for-legal9.6k3 repos~4.3kAutomated safety check: PassApache-2.0
Tw Formal WritingImbad0202/tw-formal-writing179—~1kAutomated safety check: PassMIT

Similar skills

  • Contract Review

    evolsb/claude-legal-skill

    Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.

    464 GitHub starsUsed in 1 repo~3.6k tokens
    Legal & ComplianceAuto-check passed
  • Commercial Legal Pl

    apiotrowski-afk/commercial-legal-pl

    Skill do analizy i tworzenia umów według polskiego prawa, ze szczególnym uwzględnieniem umów B2B, IP i IT (body leasing, NDA, wdrożenia, SaaS, przeniesienie praw autorskich, ugody).

    176 GitHub starsUsed in 1 repo~4.1k tokens
    Legal & ComplianceAuto-check passed
  • Hand Drawn

    threerocks/hand-drawn-styles

    A skill your agent uses when users ask for a hand-drawn or illustrated image prompt, name one of the repository's 20 numbered styles or the 3.1 stable variant, or mention triggers such as…

    2.2k GitHub stars~398 tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Legal & ComplianceAuto-check passed
  • Tw Formal Writing

    Imbad0202/tw-formal-writing

    台灣正式文件撰寫助手 — 涵蓋政府公文、政府機關其他文件、法律文件、人民對政府文書四類中文正式文件的撰寫(不含學術論文、商業文書、私人書信等,見下方排除清單)。

    179 GitHub stars~1k tokensUpdated 15 days ago
    Legal & ComplianceAuto-check passed
  • Contract Review Pro

    CSlawyer1985/contract-review-pro

    专业合同审核 Skill:7步工作流(含立场声明、框架审阅、类型路由)、5类通用门禁+16个专项门禁、终稿三件套+HTML可视化报告、8维度风险评分、修订5分类路由。完全自包含,零外部依赖。

    276 GitHub stars~2.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    886 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    886 GitHub stars~4.2k tokensUpdated 2 days ago
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    886 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    886 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Contract Review

What does Contract Review do?

Contract review assistant analyzing agreements against playbooks. Contract Review is an agent skill from borghei/Claude-Skills. Contract review assistant analyzing agreements against playbooks.

When should I use Contract Review?

Contract Review fits situations like: reviewing vendor contracts; saaS agreements; service agreements; generating redline suggestions.

How do I install Contract Review in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill contract-review -a claude-code`. Or copy the skill folder (legal/contract-review in borghei/Claude-Skills) into .claude/skills/contract-review in your project. Claude Code loads it when a task matches its description.

How do I install Contract Review in Codex?

Run `npx skills add borghei/Claude-Skills --skill contract-review -a codex`. Or copy the skill folder (legal/contract-review in borghei/Claude-Skills) into .agents/skills/contract-review in your project. Codex loads it when a task matches its description.

Can I use Contract Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill contract-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contract-review, .gemini/skills/contract-review, .github/skills/contract-review and .opencode/skills/contract-review in your project.

What does Contract Review need to run?

Going by SKILL.md and its folder, Contract Review needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Contract Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Contract Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Contract Review use?

Contract Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Contract Review use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.9k tokens, read only when the agent opens those files.

What are the alternatives to Contract Review?

Skills that share tags, products or a category with Contract Review: Contract Review (evolsb/claude-legal-skill, 464 stars), Commercial Legal Pl (apiotrowski-afk/commercial-legal-pl, 176 stars), Hand Drawn (threerocks/hand-drawn-styles, 2.2k stars) and Tabular Document Review (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Contract Review?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.