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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.0w
- Forks
- 2.0k
01 前言 Front Matter
- name
- review
- description
- 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.
- argument-hint
- [file path | Drive link | [CLM ID] | paste text]
03 SKILL.md 正文
/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
-
Load
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. If placeholders present, stop and prompt: "Run/commercial-legal:cold-start-interviewfirst — 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 astrue. -
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:
- 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.
-
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:
- 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.
-
Confirm routing if enabled.
If
confirm_routingistruein~/.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_routingisfalse: 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.mdmatrix, invoke escalation-flagger to route and draft the ask. -
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.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.