Review

anthropics/claude-for-legal/commercial-legal/skills/review

作者 anthropics4a6c651889c97cc9140580363c73e0eb17379c2b无许可证9.6K 个星标收录于 2026年10月9日更新于 2026年10月9日仓库9天前更新

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.

精选仅含说明Business & Finance
AI 生成的概览

将收到的合同路由到合适的审查技能,并把结果整合成一份审查备忘录。

功能
读取收到的协议的标题和附件以识别其结构,然后选择匹配的审查技能,例如 nda-review、vendor-agreement-review 或 saas-msa-review。它可选择先与用户确认路由,按顺序运行所选技能,并将其输出整合为一份备忘录。它还会检查升级阈值,并提供后续选项,如利益相关方摘要或修订稿。
适用场景
当用户要求审查合同、MSA、NDA 或 SaaS 协议,或附上待审查的协议时使用。它是决定适用哪个专门审查技能的入口。
运行要求
需要位于 ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md 的已配置操作手册文件,以及所引用的审查技能(nda-review、vendor-agreement-review、saas-msa-review、escalation-flagger)。协议可来自文件路径、Drive 链接、CLM ID 或粘贴文本。不附带脚本。

/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 containsSkill
    Non-Disclosure, NDA, Confidentiality Agreement (as the main agreement)nda-review
    Master Services Agreement, Professional Services, Statement of Work, Consulting Agreementvendor-agreement-review
    Subscription, SaaS, Cloud Services, Order Form with auto-renewal, Software License with recurring feessaas-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.

来源与署名

来源:anthropics/claude-for-legal位于commercial-legal/skills/review提交4a6c651

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架