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.
MCP get_skill({ skillId: "review-f82446ae" })Use this skill with your agent
Create a free account and connect via MCP
# /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 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. 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`: ```markdown ## 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.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Termination Review
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.
Brief Section Drafter
Draft a brief section in house style, consistent with the case theory — every fact cited, every case checked, every argument tied to the theory. Use when the user says "draft the [section]", "write the statement of facts", "argument section on [issue]", or needs a first draft of a brief section.
Clearance
Trademark clearance first pass — knockout + similar-marks check producing a flag list, not a clearance opinion. Use when a new mark is proposed, when asked whether a mark is available or to run a knockout search, or when assessing likelihood-of-confusion factors before a full professional search. This skill never concludes a mark is clear.