MCPInstall

review

Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.

Installs
728
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/anthropics/claude-for-legal --skill review
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads review automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

/review

Reviews an inbound agreement against the playbook in ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. Identifies the agreement structure from titles, selects the appropriate skill(s), and — if confirm_routing is enabled — checks with the user before proceeding.

Instructions

  1. Load ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. If placeholders present, stop and prompt: "Run /commercial-legal:cold-start-interview first — I need to learn your playbook before I can review against it."

    Also read ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md → ## Review preferences → confirm_routing. If the field is missing, treat it as true.

  2. Get the agreement: From file path, Drive link, [CLM ID], or pasted text. If none provided, ask.

  3. Read the document structure — titles first.

    Before reading the body, extract:

    • The main agreement title (e.g., "Master Services Agreement", "Non-Disclosure Agreement")
    • All exhibit, schedule, addendum, and attachment titles (e.g., "Exhibit A — Data Processing Addendum", "Schedule 1 — Subscription Order Form", "Annex B — Service Level Agreement")

    This is the routing signal. Do not rely on body keywords alone — a 40-page MSA with "confidential" throughout is not an NDA.

  4. Select the skill(s) based on document structure.

    Map each identified document or section to a skill:

    Document / section title containsSkill
    Non-Disclosure, NDA, Confidentiality Agreement (as the main agreement)nda-review
    Master Services Agreement, Professional Services, Statement of Work, Consulting Agreementvendor-agreement-review
    Subscription, SaaS, Cloud Services, Order Form with auto-renewal, Software License with recurring feessaas-msa-review (overlay on vendor-agreement-review)
    Data Processing Addendum, DPA, Data Processing Agreement (as exhibit or standalone)note for vendor-agreement-review → data protection section
    Service Level Agreement, SLA (as exhibit)note for saas-msa-review → SLA section

    Multiple skills may apply. Common combinations:

    • MSA + DPA exhibit → vendor-agreement-review, with DPA noted
    • SaaS subscription + Order Form + SLA exhibit → saas-msa-review (covers all three)
    • MSA + Order Form with auto-renewal → vendor-agreement-review + saas-msa-review overlay

    When the structure is genuinely ambiguous after reading titles (e.g., a document titled "Agreement" with no exhibits listed), read the first two pages of the body to resolve it — then stop and route.

  5. Confirm routing if enabled.

    If confirm_routing is true in ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md (or field is absent):

    I'm going to review this as: [agreement type(s)].
    
    Documents identified:
    - [Main agreement title] → [skill]
    - [Exhibit A title] → [how it will be handled]
    - [Exhibit B title] → [how it will be handled]
    
    Sound right? (yes / no — or tell me what I got wrong)
    

    Wait for confirmation before proceeding. If the user corrects the routing, apply their instruction and proceed.

    If confirm_routing is false: proceed silently. Log the routing decision at the top of the review memo so the user can see what was applied.

  6. Run the skill(s). Follow each skill's workflow fully. If multiple skills apply, run them in sequence and integrate the output into a single memo — don't produce separate memos.

  7. Check for escalations: If any issue exceeds the reviewer's authority per the ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md matrix, invoke escalation-flagger to route and draft the ask.

  8. Offer follow-ups:

    • Stakeholder summary for the business owner
    • Redline .docx with tracked changes
    • [CLM] record creation (if connected)
    • Add to renewal register (if auto-renewal found)

Configuring confirm_routing

Add to ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md → ## Review preferences:

## Review preferences

confirm_routing: true   # Set to false to skip routing confirmation and proceed automatically

The cold-start interview should ask about this preference. Default is true — confirmation on. As trust builds, the user can set it to false.

Examples

/commercial-legal:review vendor-msa.pdf
/commercial-legal:review https://drive.google.com/file/d/ABC123
/commercial-legal:review
[paste agreement text]

Output

Full review memo per the skill's format. Routing decision logged at the top. Deviation-by-deviation, specific redline language, named approver. Saved where ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md → House style says work product goes.

FAQ

What does the review skill do?

Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.

How do I install review?

Run npx skills add https://github.com/anthropics/claude-for-legal --skill review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review/ (personal) or .claude/skills/review/ (project).

Which AI agents can use review?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is review safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains review?

It is published by anthropics in anthropics/claude-for-legal, and it is an official skill from the maker of the technology it covers. It has 728 recorded installs.

More from anthropics/claude-for-legal

View all →

legal-writing

anthropics/claude-for-legal

Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".

OfficialBusiness & Finance1.3K installs

draft

anthropics/claude-for-legal

First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.

OfficialEducation & Science895 installs

flashcards

anthropics/claude-for-legal

Generate or drill flashcards for black-letter memorization — Leitner-style buckets, per-subject markdown storage, drill mode with self-assessment. Use when the user says "drill flashcards", "make flashcards from", "quiz me on cards", or wants to memorize rules.

OfficialDocs & Writing774 installs

saas-msa-review

anthropics/claude-for-legal

Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.

OfficialCode Quality & Workflow752 installs

policy-monitor

anthropics/claude-for-legal

Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.

OfficialBusiness & Finance707 installs

study-plan

anthropics/claude-for-legal

Build or update a long-term bar prep (or exam prep) study plan — phases, subjects weighted by weakness, daily session schedule, adaptive to session history in study-plan.yaml. Use when the user says "build a study plan", "plan my bar prep", "schedule my studying", or "how should I study for [X]".

OfficialCode Quality & Workflow706 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.