nda-review

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

NDA Review

NDA审核

Matter context

事项上下文

Matter context. Check

## Matter workspaces

in the practice-level CLAUDE.md. If

Enabled

✗

(the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run

/commercial-legal:matter-workspace switch <slug>

or say

practice-level

." Load the active matter's

matter.md

for matter-specific context and overrides. Write outputs to the matter folder at

~/.claude/plugins/config/claude-for-legal/commercial-legal/matters/<matter-slug>/

. Never read another matter's files unless

Cross-matter context

on

事项上下文：查看业务层面CLAUDE.md中的

## Matter workspaces

部分。如果“Enabled”为

✗

（内部用户默认设置），则跳过本段剩余内容——技能使用业务层面的上下文，事项机制不可见。如果已启用且没有活跃事项，请询问：“这是针对哪个事项的？运行

/commercial-legal:matter-workspace switch <slug>

或说明

practice-level

。”加载活跃事项的

matter.md

以获取特定于事项的上下文和覆盖规则。将输出写入事项文件夹：

~/.claude/plugins/config/claude-for-legal/commercial-legal/matters/<matter-slug>/

。除非

Cross-matter context

为开启状态，否则切勿读取其他事项的文件。

Destination check

目标对象检查

Before producing output, check where it's going. If the user has named a destination (a channel, a distribution list, a counterparty, "everyone"), ask whether it's inside the privilege circle. Public channels, company-wide lists, counterparty/opposing counsel, vendors, and clients (for work product) waive the protection. When the destination looks outside the circle, flag it and offer (a) the privileged version for legal only, (b) a sanitized version for the broader channel, or (c) both — don't silently apply a privileged header and then help paste it somewhere the header won't protect it. See the canonical

## Shared guardrails → Destination check

in this plugin's CLAUDE.md.

在生成输出之前，检查输出的目标对象。如果用户指定了目标对象（如频道、邮件列表、交易对手、“所有人”），请询问该对象是否属于保密范围。公开频道、公司全员列表、交易对手/对方律师、供应商以及客户（针对工作成果）会丧失保密保护。当目标对象看起来在保密范围之外时，需进行标记并提供以下选项：(a) 仅供法务使用的保密版本，(b) 适用于更广泛频道的脱敏版本，或(c) 同时提供两者——切勿默默添加保密页眉后，将其粘贴到页眉无法提供保护的地方。请参阅本插件CLAUDE.md中的标准

## Shared guardrails → Destination check

部分。

Purpose

目的

Most inbound NDAs are fine. A few have landmines. This skill sorts them in under a minute so legal only reads the ones that matter.

The goal: a GREEN NDA should need nothing more than a signature. A YELLOW needs a lawyer's eyes on one or two specific things. A RED stops before anyone wastes time.

大多数收到的NDA都没有问题，但少数存在隐患。本技能可在一分钟内完成分类，让法务仅需审核真正重要的NDA。

目标：绿色NDA只需签署即可；黄色NDA需要律师关注一两个特定问题；红色NDA需立即停止，避免浪费时间。

Load the playbook first

先加载操作手册

Which side? Before applying the playbook, determine which side the company is on for this NDA. Usually obvious from the context: if the counterparty is a vendor or partner evaluating your product, you're sales-side; if you're evaluating theirs, you're purchasing-side. Mutual NDAs still have a side — whose paper is it, and which direction is the evaluation running. If it's not obvious, ask. Read the matching playbook section (

### Sales-side playbook

### Purchasing-side playbook

) from the config. Note which side in the output so the reviewer knows which playbook was applied. If the matching side is

[Not configured]

, stop and tell the user to run

/commercial-legal:cold-start-interview --side <side>

before this triage can proceed.

Before triaging anything, read
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
→
## Playbook
→ the matching side →
NDA triage positions
. That section is the source of truth for what makes an NDA GREEN, YELLOW, or RED for this team on this side. This skill does not ship with default positions on NDA terms — the law, the market, and each team's risk tolerance vary too much for hardcoded defaults to be safe.

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

doesn't have an

NDA triage positions

section yet, or it's silent on a term that comes up in the NDA you're reviewing, ask the user:

Your playbook doesn't cover [term — e.g., "residuals clauses," "survival period," "one-way NDAs where you're the receiver"]. What's your default position — when should this be GREEN, when YELLOW, when RED? I'll add it to
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
so the next review is consistent.

Then record the answer in

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

and proceed with the triage using the new position.

**哪一方？**在应用操作手册之前，确定公司在本次NDA中的角色。通常从上下文即可明确：如果交易对手是评估我方产品的供应商或合作伙伴，我方为销售方；如果我方评估对方产品，我方为采购方。双向NDA仍有角色区分——是谁提供的文档，评估方向是什么。如果不明确，请询问。从配置中读取匹配的操作手册章节（

### Sales-side playbook

或

### Purchasing-side playbook

）。在输出中注明角色，以便审核者了解应用的是哪份操作手册。如果匹配的角色显示为

[Not configured]

，请停止操作并告知用户：在进行分类之前，请运行

/commercial-legal:cold-start-interview --side <side>

。

**在进行任何分类之前，请阅读

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

→

## Playbook

→ 匹配的角色 →

NDA triage positions

。**该部分是判断NDA属于绿色、黄色还是红色的唯一依据，适用于本团队在当前角色下的情况。本技能未预设NDA条款的默认判断标准——由于法律、市场以及各团队风险承受能力差异较大，硬编码默认标准并不安全。

如果

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中尚未包含

NDA triage positions

部分，或者该部分未涵盖当前NDA中出现的条款，请询问用户：

您的操作手册未涵盖[条款——例如：“剩余条款”、“存续期限”、“我方作为接收方的单向NDA”]。您的默认判断标准是什么？该条款何时为绿色、何时为黄色、何时为红色？我会将其添加到
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md
中，以便后续审核保持一致。

然后将答案记录到

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中，并使用新的判断标准继续分类。

Scope check

范围检查

Before reviewing NDA-specific provisions, check whether the document is doing more than its name suggests. Mutual commercial NDAs can hide: standstills, licensing grants, exclusivity, non-solicits, non-competes, IP assignments, right of first refusal, most-favored-nation clauses, and arbitration/jurisdiction clauses that govern far more than confidentiality disputes.

If the NDA contains obligations beyond confidentiality: auto-YELLOW regardless of the NDA-term analysis. Flag the non-NDA provisions:

This document is labeled an NDA but contains [standstill / license grant / non-solicit / exclusivity / IP assignment / ROFR / MFN / broad arbitration]. It's more than an NDA. Route for attorney review.

Do not silently push a document labeled "NDA" through NDA triage when the substantive obligations are a services agreement, a term sheet, or a covenant package in NDA clothing.

**在审核NDA特定条款之前，请检查文档是否超出其名称所涵盖的范围。**双向商业NDA可能隐藏以下内容：禁止竞争条款、许可授予、排他性条款、禁止挖人条款、竞业禁止条款、知识产权转让、优先购买权、最惠国条款，以及管辖范围远超保密纠纷的仲裁/管辖权条款。

如果NDA包含保密义务之外的其他义务：无论NDA条款分析结果如何，自动标记为黄色。标记非NDA条款：

本文档标注为NDA，但包含[禁止竞争条款/许可授予/禁止挖人条款/排他性条款/知识产权转让/优先购买权/最惠国条款/宽泛仲裁条款]。它不仅仅是一份NDA，请转交律师审核。

切勿将标注为“NDA”但实质义务属于服务协议、条款清单或伪装成NDA的契约包的文档，通过NDA分类流程。

The triage

分类流程

Classify the NDA into one of three buckets by applying the positions from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. The bucket definitions below are stable; the criteria that fill each bucket come from the playbook.

通过应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的判断标准，将NDA分为三类。以下分类定义是固定的；填充每一类的标准来自操作手册。

GREEN — route to signature

绿色 → 提交签署

The NDA satisfies every position in the team's playbook, and no term triggers a RED flag per the playbook. Examples of checks the playbook typically covers: mutuality, term length, survival period, carveouts, governing law, restrictive covenants, fee-shifting. Confirm each one against

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

before calling GREEN.

GREEN requires attorney-reviewed playbook positions. GREEN is the only path to signature without lawyer review. It cannot be issued against default or absent positions. Before issuing GREEN, check: does the practice profile have an attorney-reviewed

## NDA triage positions

section? If not:

I can't issue GREEN without attorney-reviewed NDA positions in your practice profile. Run
/commercial-legal:cold-start-interview --full
with your commercial counsel to set them, or route this NDA for attorney review. Issuing GREEN against defaults means a non-lawyer set the positions the next non-lawyer relies on.

Do not route to signature on defaults. YELLOW is the right call when positions are missing — it surfaces the NDA to a human who can decide.

Output:

Prepend the work-product header from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

## Outputs

(it differs by user role — see

## Who's using this

markdown

[WORK-PRODUCT HEADER — per plugin config ## Outputs]

NDA符合团队操作手册中的所有判断标准，且没有任何条款触发操作手册中的红色标记。操作手册通常涵盖的检查项示例：双向性、期限长度、存续期限、例外条款、管辖法律、限制性契约、费用转移。在标记为绿色之前，请对照

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

确认每一项。

绿色分类需要经过律师审核的操作手册判断标准。绿色是无需律师审核即可提交签署的唯一路径。不能基于默认或缺失的判断标准标记为绿色。在标记为绿色之前，请检查：业务配置文件是否包含经过律师审核的

## NDA triage positions

部分？如果没有：

在您的业务配置文件中没有经过律师审核的NDA判断标准，我无法标记为绿色。请与您的商务法律顾问一起运行
/commercial-legal:cold-start-interview --full
来设置标准，或转交该NDA给律师审核。基于默认标准标记为绿色意味着非律师人员设置的标准会被其他非律师人员依赖。

切勿基于默认标准提交签署。当判断标准缺失时，正确的选择是标记为黄色——将NDA提交给可以做出决策的人员。

输出：

从

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

的

## Outputs

部分添加工作成果页眉（根据用户角色不同而有所差异——请参阅

## Who's using this

）。

markdown

[工作成果页眉 — 按照插件配置## Outputs]

NDA Triage: [Counterparty]

NDA分类：[交易对手]

GREEN — route to signature

绿色 → 提交签署

Executive Summary

执行摘要

No red flags identified under the playbook. Route for signature per standard process.

Check	Status	Playbook reference
[Each playbook check]	[pass/fail]	[ `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` section]

Next step: [Submit to [CLM] standard NDA workflow | Send to [approver from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

] for signature]


**Before proceeding past GREEN to signature:** Read `## Who's using this` in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. If the Role is Non-lawyer:

> This step has legal consequences (countersigning an NDA binds the company). Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
>
> [Generate a 1-page summary: counterparty, NDA direction (mutual / one-way), the playbook checks run, anything the playbook didn't cover, what could go wrong if signed as-is, and the three things to ask the attorney.]
>
> If you need to find an attorney, solicitor, barrister, or other authorised legal professional: contact your professional regulator (state bar in the US, SRA/Bar Standards Board in England & Wales, Law Society in Scotland/NI/Ireland/Canada/Australia, or your jurisdiction's equivalent) for a referral service.

Do not proceed past this gate without an explicit yes.

未发现操作手册中列出的红色标记。按照标准流程提交签署。

检查项	状态	操作手册参考
[每项操作手册检查项]	[通过/未通过]	[ `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` 章节]

下一步：[提交至[CLM]标准NDA工作流 | 发送给[

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的审批人]签署]


**在标记为绿色并提交签署之前**：阅读`~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`中的`## Who's using this`部分。如果角色为非律师：

> 此步骤具有法律后果（签署NDA会约束公司）。您是否已与律师审核过此内容？如果是，请继续。如果否，请使用以下摘要咨询律师：
>
> [生成1页摘要：交易对手、NDA类型（双向/单向）、已执行的操作手册检查项、操作手册未涵盖的内容、按原样签署可能存在的风险，以及需要询问律师的三个问题。]
>
> 如果您需要寻找律师、事务律师、出庭律师或其他授权法律专业人士：联系您所在地区的专业监管机构（美国州律师协会、英格兰及威尔士律师监管局/律师标准委员会、苏格兰/北爱尔兰/爱尔兰/加拿大/澳大利亚律师协会，或您所在司法管辖区的等效机构）获取推荐服务。

未经明确确认，请勿继续此步骤。

YELLOW — needs a lawyer's eyes on specific items

黄色 → 需要律师关注特定事项

One or more terms deviate from the playbook but aren't categorical deal-breakers, OR a term appears that the playbook doesn't address. Surface each item individually so the approver can make the call.

Output:

Prepend the work-product header from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

## Outputs

(it differs by user role — see

## Who's using this

markdown

[WORK-PRODUCT HEADER — per plugin config ## Outputs]

一个或多个条款偏离操作手册，但并非绝对的交易障碍，或者出现操作手册未涵盖的条款。需逐一列出每个事项，以便审批人做出决策。

输出：

从

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

的

## Outputs

部分添加工作成果页眉（根据用户角色不同而有所差异——请参阅

## Who's using this

）。

markdown

[工作成果页眉 — 按照插件配置## Outputs]

NDA Triage: [Counterparty]

NDA分类：[交易对手]

YELLOW — flag for [approver name from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

]

黄色 → 标记给[

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的审批人姓名]

Executive Summary

执行摘要

[One-line actionable edit, e.g. "Strike non-solicit clause (Section 6)"]
[One-line actionable edit]

[一行可操作编辑建议，例如：“删除禁止挖人条款（第6条）”]
[一行可操作编辑建议]

Flagged items

标记事项

1. [Issue] — Section [X] What: [one line] Why flagged: [one line — which playbook position this hits, or "playbook is silent on this"] Legal risk: [🔴/🟠/🟡/🟢] | Business friction: [🔴 Blocks deals / 🟠 Slows deals / 🟡 Confuses customers / 🟢 Invisible] Likely resolution: [accept / push back on X / depends on deal context]

[repeat for each flag]

1. [问题] — 第[X]条内容：[一行说明] 标记原因：[一行说明——涉及操作手册中的哪项判断标准，或“操作手册未涵盖此内容”] 法律风险：[🔴/🟠/🟡/🟢] | 业务影响：[🔴 阻碍交易 / 🟠 延缓交易 / 🟡 混淆客户 / 🟢 无影响] 可能的解决方案：[接受 / 针对X进行协商 / 取决于交易背景]

[重复上述格式列出每个标记事项]

Everything else

其他合规项

Check	Status	Playbook reference
[playbook checks that passed]	pass	[ `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` section]

Next step: Ask [approver] about the flagged items, then route to signature if they're okay with it.

undefined

检查项	状态	操作手册参考
[通过的操作手册检查项]	通过	[ `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` 章节]

下一步：向[审批人]询问标记事项，若获得批准则提交签署。

undefined

RED — stop, talk to legal first

红色 → 停止，先咨询法务

The NDA hits a position on the playbook's "never accept" list, or the structure of the agreement is incompatible with the team's standard posture (e.g., a one-way NDA where the team's playbook requires mutual; a perpetual term where the playbook caps at a finite period; governing law on the "never" list).

Output:

Prepend the work-product header from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

## Outputs

(it differs by user role — see

## Who's using this

markdown

[WORK-PRODUCT HEADER — per plugin config ## Outputs]

NDA触发了操作手册中的“绝不接受”列表中的判断标准，或协议结构与团队的标准立场不符（例如：团队操作手册要求双向，但实际为单向NDA；操作手册规定有限期限，但实际为永久期限；管辖法律属于“绝不接受”列表）。

输出：

从

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

的

## Outputs

部分添加工作成果页眉（根据用户角色不同而有所差异——请参阅

## Who's using this

）。

markdown

[工作成果页眉 — 按照插件配置## Outputs]

NDA Triage: [Counterparty]

NDA分类：[交易对手]

RED — do not submit, talk to legal first

红色 → 请勿提交，先咨询法务

Executive Summary

执行摘要

[One-line actionable edit, e.g. "Section 4 — route to Legal for review"]
[One-line actionable edit]

[一行可操作建议，例如：“第4条 — 转交法务审核”]
[一行可操作建议]

Critical issues

关键问题

1. [Issue] — Section [X]

"[exact quote]" Why this is a problem: [specific risk; cite the playbook position it violates] Legal risk: [🔴/🟠/🟡/🟢] | Business friction: [🔴 Blocks deals / 🟠 Slows deals / 🟡 Confuses customers / 🟢 Invisible] Recommended response: [use our paper instead | push back with specific language | walk]

Next step: Send this triage to [GC or named escalation person from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

]. Do not send to [CLM or approvals workflow]. Do not tell the counterparty we'll sign.

undefined

1. [问题] — 第[X]条

"[原文引用]" 问题原因：[具体风险；引用违反的操作手册判断标准] 法律风险：[🔴/🟠/🟡/🟢] | 业务影响：[🔴 阻碍交易 / 🟠 延缓交易 / 🟡 混淆客户 / 🟢 无影响] 建议应对措施：[使用我方文档 / 针对特定内容进行协商 / 终止谈判]

下一步：将此分类结果发送给[

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的首席法务官或指定升级负责人]。请勿发送至[CLM或审批工作流]。请勿告知交易对手我方会签署。

undefined

Redline granularity

修改粒度

Edit at the smallest possible granularity. A redline is a negotiation artifact, not a rewrite. Wholesale clause replacement signals "we threw out your drafting" — it's aggressive, it forces the counterparty to re-read the whole clause, and it discards the parts of their drafting that were fine. Surgical redlines — strike a word, insert a phrase, restructure a subclause — signal "we have specific asks" and are faster to read, understand, and accept.

Default to the smallest edit that achieves the playbook position:

Replace a word before a phrase. ("twelve (12)" → "twenty-four (24)")
Replace a phrase before a sentence. ("paid by the Buyer" → "paid and payable by the Buyer")
Restructure a subclause before replacing the sentence. (Add "(a)" and "(b)" to split a compound condition.)
Replace a sentence before replacing the clause.
Only replace a whole clause when the counterparty's version is so far from your position that surgical edits would be harder to read than a fresh draft — and when you do, say so in the transmittal: "We've replaced §8.2 rather than marking it up because the changes were extensive. Happy to walk you through the delta."

When in doubt, smaller. A client who receives a surgical redline trusts that you read carefully. A client who receives a wholesale replacement wonders whether you read at all.

尽可能以最小粒度进行修改。修改标记是谈判的产物，而非重写。整段替换条款意味着“我们否决了您的起草内容”——这种方式过于强硬，会迫使交易对手重新阅读整个条款，并且会丢弃对方起草中合理的部分。精准修改——删除一个词、插入一个短语、调整子条款结构——意味着“我们有特定的诉求”，更易于阅读、理解和接受。

默认采用最小粒度的修改来满足操作手册的判断标准：

先替换单个词，再替换短语。（“twelve (12)” → “twenty-four (24)”）
先替换短语，再替换句子。（“paid by the Buyer” → “paid and payable by the Buyer”）
先调整子条款结构，再替换句子。（添加“(a)”和“(b)”拆分复合条件。）
先替换句子，再替换条款。
仅当对方的条款版本与我方立场相差甚远，精准修改比重新起草更难理解时，才替换整个条款——此时需在传输说明中注明：“我们替换了第8.2条，而非标记修改，因为变更内容较多。如需了解差异，我们很乐意进行说明。”

如有疑问，优先选择更小粒度的修改。收到精准修改的客户会相信您仔细阅读了文档；而收到整段替换的客户会怀疑您是否阅读过文档。

Jurisdiction assumption

司法管辖区假设

This triage applies the governing-law and restrictive-covenant positions recorded in

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. Legal rules (enforceability of non-competes, non-solicits, fee-shifting, choice of law) vary materially by jurisdiction. If the NDA involves a jurisdiction outside the team's configured posture, flag it in the output and note that the triage may not transfer as written.

本分类流程应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中记录的管辖法律和限制性契约判断标准。法律规则（竞业禁止、禁止挖人、费用转移、法律选择的可执行性）因司法管辖区而异。如果NDA涉及团队配置立场之外的司法管辖区，请在输出中标记，并注明本分类结果可能无法直接适用。

Output rules

输出规则

Complexity filter: If addressing an issue would require drafting new language, restructuring a clause, or inserting substantive new provisions — do not attempt it. Instead write: "Section [X] — route to Legal for review." Only include simple, mechanical actions in the Executive Summary (strike, delete, replace a word or phrase).

Clean NDA rule: If the NDA passes all checks with no flags, the Executive Summary should say only: "No red flags identified. Route for signature per standard process."

Do not produce a lengthy report for a clean NDA.

复杂度过滤：如果解决某个问题需要起草新内容、调整条款结构或插入实质性新条款——请勿尝试。请改为：“第[X]条 — 转交法务审核。”执行摘要中仅包含简单的机械操作（删除、移除、替换一个词或短语）。

简洁NDA规则：如果NDA通过所有检查且无标记，执行摘要应仅说明：“未发现红色标记。按照标准流程提交签署。”

请勿为合规的NDA生成冗长报告。

Detailed check reference

详细检查参考

For each check below, the bucket (GREEN/YELLOW/RED) is determined by

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. This skill lists the categories to check; it does not hardcode thresholds.

对于以下每项检查，分类（绿色/黄色/红色）由

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

确定。本技能列出需要检查的类别；未硬编码阈值。

Mutuality

双向性

Is the NDA mutual or one-way? Apply the team's position from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. If the playbook doesn't address one-way NDAs for this context, run the one-way questionnaire below and surface the result for a human.

One-way NDA questionnaire

When the NDA is unilateral (one party discloses, the other only receives), do not immediately flag RED or exit. Ask:

A one-way NDA is appropriate in some situations. Before flagging this, let me ask a few quick questions:

In this relationship, are you the only party disclosing confidential information? (i.e., the other side shares nothing back)

Is this for a limited, specific disclosure — for example, sharing your technology with a vendor who will work on it, but not sharing theirs with you?

Is this related to M&A, employment, or investment? (If yes, stop — this skill is for commercial MNDAs only. Route to Legal.)

Use the answers plus the

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

position to decide GREEN/YELLOW/RED. If

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

doesn't take a position on this fact pattern, flag YELLOW and surface the questionnaire answers for the approver.

NDA是双向还是单向？应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的团队判断标准。如果操作手册未涵盖此场景下的单向NDA，请运行以下单向NDA问卷，并将结果提交给人工审核。

单向NDA问卷

当NDA为单向（一方披露信息，另一方仅接收）时，请勿立即标记为红色或终止操作。请询问：

单向NDA在某些情况下是合适的。在标记之前，请让我问几个简单的问题：

在本次合作中，是否只有我方披露保密信息？（即对方不向我方提供任何信息）

这是否针对有限的特定披露——例如，向供应商分享我方技术以便其开展工作，但对方不向我方分享其技术？

这是否与并购、雇佣或投资相关？（如果是，请停止——本技能仅适用于商业双向NDA。转交法务审核。）

结合答案和

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的判断标准，决定分类为绿色/黄色/红色。如果

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

未针对此情况设定判断标准，请标记为黄色，并将问卷结果提交给审批人。

Definition of Confidential Information

保密信息定义

Check scope (marked-only vs. everything-disclosed), marking requirements, and oral-disclosure confirmation windows. Apply the team's position from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. If the playbook is silent on any of these, ask.

检查范围（仅标记的信息 vs. 所有披露的信息）、标记要求以及口头披露的确认期限。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的团队判断标准。如果操作手册未涵盖其中任何一项，请询问。

Carveouts

例外条款

The five carveouts typically present in an NDA:

Information that is or becomes public (other than through breach)
Information the receiving party already had
Information independently developed without reference to the CI
Information received from a third party without restriction
Information required to be disclosed by law or court order (with notice to discloser where legally permitted)

Which carveouts the team requires, and how strictly, is a playbook question. Check

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

for the team's position on required carveouts, acceptable variations in wording, and what happens when one is missing.

NDA中通常包含的五项例外条款：

已公开或非因违约而公开的信息
接收方已拥有的信息
接收方未参考保密信息独立开发的信息
接收方从第三方无限制获取的信息
法律或法院命令要求披露的信息（在法律允许的情况下，需通知披露方）

团队要求哪些例外条款，以及严格程度如何，由操作手册决定。请检查

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中团队关于必备例外条款、可接受的措辞变体，以及缺失某项例外条款的处理方式的判断标准。

Residuals

剩余条款

A residuals clause lets the receiving party use information retained in unaided memory. Whether this is acceptable — and under what conditions (e.g., narrow "unaided memory" wording vs. broader scope covering notes or copies) — is a playbook question. Apply

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. If the playbook doesn't address residuals, ask.

剩余条款允许接收方使用未借助外部记忆工具保留的信息。是否可接受——以及在何种条件下（例如：狭义的“未借助外部记忆工具”措辞 vs. 涵盖笔记或副本的广义范围）——由操作手册决定。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的标准。如果操作手册未涵盖剩余条款，请询问。

Term and survival

期限与存续

Check the initial term length, the post-term survival period for confidentiality obligations, and whether trade secrets are carved out with longer protection. Apply the team's position from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. If the playbook doesn't cover one of these, ask.

检查初始期限长度、保密义务的到期后存续期限，以及是否将商业秘密单独列出并提供更长保护。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的团队判断标准。如果操作手册未涵盖其中任何一项，请询问。

Restrictive covenants

限制性契约

Check for non-solicits (employee, customer), non-competes, exclusivity, and any restriction on who else the receiving party can engage with. Apply

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

. If the playbook is silent, ask — restrictive covenants are jurisdiction-sensitive and the team's posture matters.

检查禁止挖人（员工、客户）、竞业禁止、排他性条款，以及任何限制接收方与其他方合作的条款。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的标准。如果操作手册未涵盖，请询问——限制性契约受司法管辖区影响较大，团队的立场至关重要。

Attorneys' fees

律师费

Check for fee-shifting provisions and whether they are mutual, one-sided, or prevailing-party. Apply

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

检查费用转移条款，以及该条款是双向、单向还是胜诉方承担。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的标准。

Backup and archival carveout

备份与存档例外条款

Check whether the destruction/return clause includes an exception for standard backup and archival retention systems. Apply the team's position from

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

— some teams require this carveout and will push to add it; others accept an NDA without it. If the playbook doesn't address this, ask.

检查销毁/返还条款是否包含标准备份和存档保留系统的例外情况。应用

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的团队判断标准——有些团队要求此例外条款，并会推动添加；有些团队则接受无此条款的NDA。如果操作手册未涵盖此内容，请询问。

Governing law

管辖法律

Per

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

## Playbook

→

Governing law and venue

按照

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中的

## Playbook

→

Governing law and venue

部分执行。

Counterparty context

交易对手上下文

BigCo NDAs: Fortune 500 counterparties generally won't negotiate NDAs. Calibrate: is the RED flag truly a deal-breaker, or is it "different from our form"? If the business relationship matters, the call is whether to accept their paper — escalate that decision, don't make it.

Startup NDAs: Will usually take our paper. If their NDA has issues, the fastest path is often "let's use ours" rather than redlining theirs.

大型企业NDA：财富500强交易对手通常不会协商NDA。请校准判断：红色标记是否真的是交易障碍，还是“与我方格式不同”？如果业务关系重要，决策在于是否接受对方的文档——请升级此决策，切勿自行决定。

初创企业NDA：通常会接受我方文档。如果对方的NDA存在问题，最快的解决方式通常是“使用我方文档”，而非修改对方的文档。

Integration: CLM

集成：CLM

If connected:

GREEN → offer to create the CLM record in the standard NDA workflow
YELLOW → offer to create it with a note attached listing the flagged items
RED → do not create a record; the lawyer decides what happens next

如果已连接：

绿色 → 提议在标准NDA工作流中创建CLM记录
黄色 → 提议创建记录并附加标记事项列表
红色 → 请勿创建记录；由律师决定下一步操作

What this skill does NOT do

本技能不执行的操作

It does not negotiate. It sorts.
It does not draft an NDA. If the answer is "use our paper," the user pulls our form from [CLM or document system].
It does not make the call on YELLOW items. It surfaces them for a human.

It does not state a position on any NDA term. Positions live in

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

不进行谈判，仅进行分类。
不起草NDA。如果解决方案是“使用我方文档”，用户需从[CLM或文档系统]获取我方模板。
不针对黄色事项做出决策，仅提交给人工审核。

不针对任何NDA条款表明立场。立场仅存在于

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中。

Closing action

收尾操作

Read

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

→

## NDA triage preferences

→

closing_action

If configured, append the closing action verbatim at the end of every output. Example configurations:

closing_action: "Send the full text of this analysis along with a copy
of the NDA to Legal at legal@[yourcompany].com for final confirmation before
signing."

closing_action: "Submit to [CLM] using the standard NDA workflow.
Legal will confirm before routing for signature."

closing_action: "Forward this output and the NDA to your contracts
manager."

closing_action

is not configured in

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

, append: "Route final NDA through your standard approval process."

The cold-start interview asks: "When someone finishes an NDA triage, what do you want them to do with the output? I'll add that as a standing instruction at the end of every review."

阅读

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

→

## NDA triage preferences

→

closing_action

。

如果已配置，请在每个输出末尾逐字添加收尾操作。配置示例：

closing_action: "在签署之前，将本分析的完整文本以及NDA副本发送至法务邮箱legal@[yourcompany].com进行最终确认。"

closing_action: "使用标准NDA工作流提交至[CLM]。法务会在提交签署前进行确认。"

closing_action: "将此输出和NDA转发给您的合同经理。"

如果

~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md

中未配置

closing_action

，请添加： “通过标准审批流程提交最终NDA。”

初始化访谈会询问：“当完成NDA分类后，您希望用户如何处理输出？我会将其添加为每次审核末尾的固定说明。”

Close with the next-steps decision tree

以下一步决策树结束

End with the next-steps decision tree per CLAUDE.md

## Outputs

. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

按照CLAUDE.md

## Outputs

中的下一步决策树结束。根据本技能生成的内容自定义选项——五个默认分支（起草X、升级、获取更多事实、观望、其他）是起点，而非固定选项。决策树是输出内容；由律师做出选择。",