$ loading_
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.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "review" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/commercial-legal/skills/review/SKILL.md 2. Save it as ~/.claude/skills/review/SKILL.md 3. Reload skills and tell me it's ready
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.
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.
Get the agreement: From file path, Drive link, [CLM ID], or pasted text. If none provided, ask.
Read the document structure — titles first.
Before reading the body, extract:
This is the routing signal. Do not rely on body keywords alone — a 40-page MSA with "confidential" throughout is not an NDA.
Select the skill(s) based on document structure.
Map each identified document or section to a skill:
| Document / section title contains | Skill |
|---|---|
| Non-Disclosure, NDA, Confidentiality Agreement (as the main agreement) | nda-review |
| Master Services Agreement, Professional Services, Statement of Work, Consulting Agreement | vendor-agreement-review |
| Subscription, SaaS, Cloud Services, Order Form with auto-renewal, Software License with recurring fees | saas-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:
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.
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.
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.
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.
Offer follow-ups:
…
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
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.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.