.agents/skills/triage-nda/SKILL.md
Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.
npx skillsauth add mmahalwy/cooper triage-ndaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
content-media
Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).
documentation
Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.
development
Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.