$ 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.
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "review" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/commercial-legal/skills/review/SKILL.md 2. 保存为 ~/.claude/skills/review/SKILL.md 3. 装好后重载技能，告诉我可以用了
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:
…
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".
Run a focused N-question study session on a subject — MBE, essay, or flashcards. Tracks performance and updates the study plan. Use when the user says "run me 10 questions on [subject]", "do a session on [subject]", "let's do 5 cards on [subject]", or wants to drill a fixed number of questions and have the plan adapt.
Socratic drilling — it asks, you answer, it pushes back. Does NOT give you the answer until you've earned it. Use when the user says "drill me on", "quiz me", "socratic", "test me on [subject]", or wants to study actively.
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent counsel review. This skill never concludes a product is clear to launch.
Ask questions against an open investigation log — what witnesses said, where accounts conflict, what gaps exist, what the strongest evidence is on each issue. Use when the attorney needs to query the investigation record without re-reading every entry.
Termination review — high-risk flag detection, severance + release, and final pay timing by jurisdiction. Jurisdiction-specific rules and release consideration periods are researched per review, not stored. Use when the user says "reviewing a termination", "can we fire this person", "term review", or describes a termination scenario.