From legal
Triages NDAs into GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Screens for non-solicits, non-competes, residuals, and missing carveouts using playbook or defaults.
How this skill is triggered — by the user, by Claude, or both
Slash command
/legal:triage-nda <NDA file or text><NDA file or text>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
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.
npx claudepluginhub p/phil248-legal-legal5plugins reuse this skill
First indexed Jun 13, 2026
Triages NDAs into GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Screens for non-solicits, non-competes, residuals, and missing carveouts using playbook or defaults.
Screens incoming NDAs and classifies them as GREEN (standard), YELLOW (needs review), or RED (significant issues) using a structured checklist covering agreement type, confidentiality definitions, obligations, and standard carveouts.
Triage inbound NDAs into GREEN / YELLOW / RED so legal only reviews the ones that need it. Applies a configurable playbook for sales-side or purchasing-side review.