Triage Nda
Pre-screen incoming NDAs from sales or partners and route them as GREEN, YELLOW, or RED before anyone signs under the wrong delegation.
Overview
triage-nda is an agent skill for the Operate phase that classifies incoming NDAs as GREEN, YELLOW, or RED against your playbook so you can route them to approval or legal review quickly.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill triage-ndaWhat is this skill?
- GREEN / YELLOW / RED classification for fast routing
- Screens mutual vs unilateral NDAs against a local playbook
- Flags embedded non-solicits, non-competes, and missing carveouts
- Accepts PDF, DOCX, URL, or pasted text
- Explicit workflow disclaimer—not a substitute for licensed counsel
- 3-tier classification: GREEN, YELLOW, RED
Adoption & trust: 1.4k installs on skills.sh; 19.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
A new NDA landed from a prospect or partner and you cannot tell in minutes whether it is standard, risky, or needs a lawyer before anyone signs.
Who is it for?
Small SaaS teams with a written NDA playbook who repeatedly receive mutual or one-way NDAs during sales conversations.
Skip if: Builders without any screening criteria who need contract drafting, jurisdiction-specific legal opinions, or automated e-signature filing.
When should I use this skill?
A new NDA arrives from sales or BD, or you need to screen for embedded non-solicits, non-competes, or missing carveouts.
What do I get? / Deliverables
You receive a playbook-aligned triage label with highlighted clause risks and a clear routing recommendation for standard approval, counsel review, or full legal review.
- GREEN/YELLOW/RED classification
- Clause risk notes aligned to playbook
- Routing recommendation for approval path
Recommended Skills
Journey fit
Operate covers ongoing business motions—here, recurring inbound legal documents that block deals if mishandled after you are already shipping and selling. Iterate fits contract triage loops where each new NDA is reviewed, classified, and fed back into playbook updates rather than one-time product validation.
How it compares
Use as a pre-screening checker against your local playbook—not as autonomous legal advice or a CLM replacement.
Common Questions / FAQ
Who is triage-nda for?
Founders, ops leads, or sales engineers who first-touch NDAs and need consistent risk bucketing before involving counsel.
When should I use triage-nda?
Use in Operate when a new NDA arrives, when screening for non-solicits or missing carveouts, or when deciding if standard delegation signing is appropriate.
Is triage-nda safe to install?
Review the Security Audits panel on this page; never upload highly sensitive deal terms to untrusted environments, and have qualified lawyers review all classifications.
SKILL.md
READMESKILL.md - Triage Nda
# /triage-nda -- NDA Pre-Screening > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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. ## Invocation ``` /triage-nda ``` ## Workflow ### Step 1: Accept the NDA Accept the NDA in any format: - **File upload**: PDF, DOCX, or other document format - **URL**: Link to the NDA in a document system - **Pasted text**: NDA text pasted directly If no NDA is provided, prompt the user to supply one. ### Step 2: Load NDA Playbook Look for NDA screening criteria in local settings (e.g., `legal.local.md`). The NDA playbook should define: - Mutual vs. unilateral requirements - Acceptable term lengths - Required carveouts - Prohibited provisions - Organization-specific requirements **If no NDA playbook is configured:** - Proceed with reasonable market-standard defaults - Note clearly that defaults are being used - Defaults applied: - Mutual obligations required (unless the organization is only disclosing) - Term: 2-3 years standard, up to 5 years for trade secrets - Standard carveouts required: independently developed, publicly available, rightfully received from third party, required by law - No non-solicitation or non-compete provisions - No residuals clause (or narrowly scoped if present) - Governing law in a reasonable commercial jurisdiction ### Step 3: Quick Screen Evaluate the NDA against each screening criterion systematically. #### 1. Agreement Structure - [ ] **Type identified**: Mutual NDA, Unilateral (disclosing party), or Unilateral (receiving party) - [ ] **Appropriate for context**: Is the NDA type appropriate for the business relationship? (e.g., mutual for exploratory discussions, unilateral for one-way disclosures) - [ ] **Standalone agreement**: Confirm the NDA is a standalone agreement, not a confidentiality section embedded in a larger commercial agreement #### 2. Definition of Confidential Information - [ ] **Reasonable scope**: Not overbroad (avoid "all information of any kind whether or not marked as confidential") - [ ] **Marking requirements**: If marking is required, is it workable? (Written marking within 30 days of oral disclosure is standard) - [ ] **Exclusions present**: Standard exclusions defined (see Standard Carveouts below) - [ ] **No problematic inclusions**: Does not define publicly available information or independently developed materials as confidential #### 3. Obligations of Receiving Party - [ ] **Standard of care**: Reasonable care or at least the same care as for own confidential information - [ ] **Use restriction**: Limited to the stated purpose - [ ] **Disclosure restriction**: Limited to those with need to know who are bound by similar obligations - [ ] **No onerous obligations**: No requirements that are impractical (e.g., encrypting all communications, maintaining physical logs) #### 4. Standard Carveouts All of the following carveouts should be present: - [ ] **Public knowledge**: Information that is or becomes publicly available through no fault of the receiving party - [ ] **Prior possession**: Information already known to the receiving party before disclosure - [ ] **Independent development**: Information independently developed without use