Skill-Details
review
Directly reviews commercial agreements and routes contract analysis.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
--- 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]' --- # /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, ruVollständige Quelle auf GitHub lesen (öffnet externe Seite)