triage-nda by anthropics/knowledge-work-plugins
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill triage-nda如果您看到不熟悉的占位符或需要检查连接了哪些工具,请参阅 CONNECTORS.md。
对 NDA 进行预审:@$1
根据标准筛选标准快速预审收到的 NDA。对 NDA 进行分类以便路由:标准批准、律师审查或全面法律审查。
重要提示:您协助法律工作流程,但不提供法律建议。所有分析在依赖之前都应经过合格法律专业人士的审查。
/triage-nda
以任何格式接收 NDA:
如果未提供 NDA,则提示用户提供。
在本地设置(例如 legal.local.md)中查找 NDA 筛选标准。
NDA 审查手册应定义:
如果未配置 NDA 审查手册:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
根据每个筛选标准系统地评估 NDA。
应存在以下所有例外条款:
根据筛选结果,分配一个分类:
必须全部满足以下条件:
路由:通过标准授权委托批准。无需律师审查。
存在一个或多个以下情况,但 NDA 没有根本性问题:
路由:标记具体问题供律师审查。律师很可能通过一次审查修订就能解决。
存在一个或多个以下情况:
路由:需要全面法律审查。请勿签署。需要谈判、使用组织的标准格式 NDA 进行反提案或拒绝。
输出结构化报告:
## NDA 预审报告
**分类**: [绿色 / 黄色 / 红色]
**各方**: [各方名称]
**类型**: [相互 / 单方面(披露方)/ 单方面(接收方)]
**期限**: [持续时间]
**管辖法律**: [司法管辖区]
**审查依据**: [审查手册 / 默认标准]
## 筛选结果
| 标准 | 状态 | 备注 |
|-----------|--------|-------|
| 相互义务 | [通过/标记/失败] | [详情] |
| 定义范围 | [通过/标记/失败] | [详情] |
| 期限 | [通过/标记/失败] | [详情] |
| 标准例外条款 | [通过/标记/失败] | [详情] |
| [等等] | | |
## 发现的问题
### [问题 1 -- 黄色/红色]
**内容**: [描述]
**风险**: [可能出现什么问题]
**建议修复**: [具体措辞或方法]
[对每个问题重复]
## 建议
[具体后续步骤:批准、发送审查并附具体说明,或拒绝/反提案]
## 后续步骤
1. [行动项 1]
2. [行动项 2]
根据分类,建议适当的后续步骤:
| 分类 | 建议操作 | 典型时间线 |
|---|---|---|
| 绿色 | 根据授权委托批准并路由签署 | 当天 |
| 黄色 | 发送给指定审查人,并标记具体问题 | 1-2 个工作日 |
| 红色 | 请律师进行全面审查;准备反提案或标准格式 | 3-5 个工作日 |
对于黄色和红色分类:
标准立场:保密信息应限于与所述目的相关的非公开披露信息,并有明确的排除项。修订方法:将定义缩小为标记或标识为保密的信息,或根据信息的性质和披露情况,合理人士会理解为保密的信息。
标准立场:必须包含一个例外条款,针对未参考或使用披露方保密信息而独立开发的信息。如果缺失的风险:可能产生内部开发的产品或功能源自对方保密信息的索赔。修订方法:添加标准独立开发例外条款。
标准立场:禁止招揽条款不属于 NDA。它们适用于雇佣协议、并购协议或特定的商业协议。修订方法:完全删除该条款。如果对方坚持,则限制为针对性招揽(非一般招聘)并设定短期(12 个月)。
标准立场:抵制残余信息条款。如果必须,则限制为:(a) 获得授权访问的个人未经辅助记忆保留的一般想法、概念、专有技术或技术;(b) 明确排除商业秘密和可专利信息;(c) 不授予任何知识产权许可。如果过于宽泛的风险:实际上授予了为任何目的使用披露方保密信息的许可。
标准立场:自披露或终止之日起 2-5 年,以较晚者为准。商业秘密可能值得在保持商业秘密性质期间进行保护。修订方法:用明确的期限替换永久性义务。为符合条件的信息提供更长时间保护的商业秘密例外条款。
每周安装次数
191
代码库
GitHub 星标数
10.3K
首次出现
11 天前
安全审计
安装于
gemini-cli184
codex183
cursor183
opencode183
kimi-cli182
github-copilot182
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Triage the NDA: @$1
Rapidly triage incoming NDAs against standard screening criteria. Classify the NDA for routing: standard approval, counsel review, or full legal review.
Important : You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
/triage-nda
Accept the NDA in any format:
If no NDA is provided, prompt the user to supply one.
Look for NDA screening criteria in local settings (e.g., legal.local.md).
The NDA playbook should define:
If no NDA playbook is configured:
Evaluate the NDA against each screening criterion systematically.
All of the following carveouts should be present:
Based on the screening results, assign a classification:
All of the following must be true:
Routing : Approve via standard delegation of authority. No counsel review required.
One or more of the following are present, but the NDA is not fundamentally problematic:
Routing : Flag specific issues for counsel review. Counsel can likely resolve with minor redlines in a single review pass.
One or more of the following are present:
Routing : Full legal review required. Do not sign. Requires negotiation, counterproposal with the organization's standard form NDA, or rejection.
Output a structured report:
## NDA Triage Report
**Classification**: [GREEN / YELLOW / RED]
**Parties**: [party names]
**Type**: [Mutual / Unilateral (disclosing) / Unilateral (receiving)]
**Term**: [duration]
**Governing Law**: [jurisdiction]
**Review Basis**: [Playbook / Default Standards]
## Screening Results
| Criterion | Status | Notes |
|-----------|--------|-------|
| Mutual Obligations | [PASS/FLAG/FAIL] | [details] |
| Definition Scope | [PASS/FLAG/FAIL] | [details] |
| Term | [PASS/FLAG/FAIL] | [details] |
| Standard Carveouts | [PASS/FLAG/FAIL] | [details] |
| [etc.] | | |
## Issues Found
### [Issue 1 -- YELLOW/RED]
**What**: [description]
**Risk**: [what could go wrong]
**Suggested Fix**: [specific language or approach]
[Repeat for each issue]
## Recommendation
[Specific next step: approve, send for review with specific notes, or reject/counter]
## Next Steps
1. [Action item 1]
2. [Action item 2]
Based on the classification, recommend the appropriate next step:
| Classification | Recommended Action | Typical Timeline |
|---|---|---|
| GREEN | Approve and route for signature per delegation of authority | Same day |
| YELLOW | Send to designated reviewer with specific issues flagged | 1-2 business days |
| RED | Engage counsel for full review; prepare counterproposal or standard form | 3-5 business days |
For YELLOW and RED classifications:
Standard position : Confidential information should be limited to non-public information disclosed in connection with the stated purpose, with clear exclusions. Redline approach : Narrow the definition to information that is marked or identified as confidential, or that a reasonable person would understand to be confidential given the nature of the information and circumstances of disclosure.
Standard position : Must include a carveout for information independently developed without reference to or use of the disclosing party's confidential information. Risk if missing : Could create claims that internally-developed products or features were derived from the counterparty's confidential information. Redline approach : Add standard independent development carveout.
Standard position : Non-solicitation provisions do not belong in NDAs. They are appropriate in employment agreements, M&A agreements, or specific commercial agreements. Redline approach : Delete the provision entirely. If the counterparty insists, limit to targeted solicitation (not general recruitment) and set a short term (12 months).
Standard position : Resist residuals clauses. If required, limit to: (a) general ideas, concepts, know-how, or techniques retained in the unaided memory of individuals who had authorized access; (b) explicitly exclude trade secrets and patentable information; (c) does not grant any IP license. Risk if too broad : Effectively grants a license to use the disclosing party's confidential information for any purpose.
Standard position : 2-5 years from disclosure or termination, whichever is later. Trade secrets may warrant protection for as long as they remain trade secrets. Redline approach : Replace perpetual obligation with a defined term. Offer a trade secret carveout for longer protection of qualifying information.
Weekly Installs
191
Repository
GitHub Stars
10.3K
First Seen
11 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
gemini-cli184
codex183
cursor183
opencode183
kimi-cli182
github-copilot182
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
31,600 周安装
Docassemble 表单构建器技能 - 创建智能动态问卷与文档生成工具
376 周安装
App Store Connect 发布流程自动化工具:asc-release-flow 使用指南
367 周安装
asc-id-resolver:App Store Connect ID 解析工具,快速获取应用、构建、版本等ID
369 周安装
OpenAPI Specification 2.0 (Swagger 2.0) 完整指南:API 描述、验证与代码生成
364 周安装
Auth.js v5 身份验证指南 - Next.js 16 集成与安全配置
367 周安装
福格行为模型指南:提升用户留存的行为设计框架与产品优化策略
393 周安装