skills / legal & compliance

triage-nda

what it does

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.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Sales wants to sign this mutual NDA with a prospect today so we can start a technical deep dive. Anything that should stop us?”

Source material given with the request

MUTUAL NON-DISCLOSURE AGREEMENT between Orrin Analytics, Inc. and Halvard Systems Ltd. 1. Purpose. Evaluating a possible integration partnership (the "Purpose"). 2. Confidential Information means non-public information disclosed by either party that is marked confidential or that a reasonable person would understand to be confidential. 3. Exclusions. Confidential Information does not include information that (a) is or becomes public through no fault of the recipient; (b) was known to the recipient before disclosure; (c) is independently developed without use of the discloser's information; (d) is rightfully received from a third party without restriction; or (e) must be disclosed by law, provided the recipient gives prompt notice where legally permitted. 4. Use. Each party will use Confidential Information only for the Purpose and share it only with employees, contractors and advisors who need to know and are bound by similar duties. 5. Term. This Agreement lasts 2 years; obligations survive 3 years after it ends. 6. Return. On request, each party will return or destroy Confidential Information, except copies kept under legal or routine backup retention. 7. General Cooperation. During the term and for 24 months after, neither party will directly or indirectly solicit, recruit or hire any employee of the other party with whom it had contact in connection with the Purpose. 8. Governing Law. Delaware law; courts of Delaware.
with the skill
## NDA Triage Report **Classification: RED. Do not sign as drafted.** **Parties:** Orrin Analytics, Inc. / Halvard Systems Ltd. **Type:** Mutual **Term:** 2 years, with confidentiality surviving 3 years after the agreement ends **Governing Law:** Delaware law and Delaware courts **Review Basis:** Default market-standard criteria (no NDA playbook was provided) ### Screening Results | Criterion | Status | Notes | |---|---|---| | Structure | PASS | Standalone and mutual, which fits an exploratory partnership discussion. | | Definition scope | PASS | Limited to non-public information that is marked or reasonably understood to be confidential. | | Standard carveouts | PASS | All five are present: public, prior knowledge, independent development, third-party receipt and legal compulsion with notice. | | Use and disclosure | PASS | Limited to the Purpose and to need-to-know employees, contractors and advisors under similar duties. Affiliates are not mentioned, which is a minor point. | | Term | PASS | 2 years plus 3 years survival is within the standard range. | | Return and destruction | PASS | Includes a retention exception for legal and routine backup copies. | | Remedies | NOTE | No remedies clause. This is neutral and not a blocker. Counsel may want to add an equitable-relief acknowledgment. |
Show the rest (29 more lines)
| Problematic provisions | **FAIL** | Section 7 contains a non-solicit and no-hire. | | Governing law | PASS | Delaware is a well-established commercial jurisdiction, and the law and forum are consistent. No arbitration. | ### Issue Found **Section 7, "General Cooperation" (RED)** - **What:** The heading is misleading, but the clause is a mutual employee non-solicit and no-hire. It runs for the term plus 24 months, so up to 4 years. It covers indirect solicitation and also bars hiring, not just soliciting. It applies to any employee the party had "contact" with in connection with the Purpose. - **Risk:** - Restrictions on hiring and recruiting don't belong in an NDA. - The no-hire reaches inbound applicants too. If a Halvard engineer you meet in the technical deep dive later applies to Orrin, you could be in breach. - The technical deep dive will create the "contact" that triggers the restriction, and "contact" is undefined. - The restriction outlasts the actual confidentiality exchange and could affect your hiring for years. - **Suggested fix:** Delete Section 7 entirely. If Halvard insists, a fallback is to limit it to targeted solicitation (not general recruiting or job postings), remove the "hire" language, carve out inbound applicants, and cap it at 12 months. ### Recommendation Do not sign today as drafted. Everything else is clean, so this should be fast. Send Halvard a one-line redline that deletes Section 7. If they accept, the NDA would classify as GREEN and could be signed the same day. ### Next Steps 1. Tell Sales the only blocker is Section 7, and that a quick redline can still make today feasible. 2. Send the redline to Halvard: strike Section 7 and say that non-solicit terms aren't something Orrin includes in NDAs. 3. Route to counsel or your designated reviewer. They should approve the fallback position in advance if you want to negotiate rather than only strike. 4. Optionally ask counsel to add a standard equitable-relief clause and an affiliates reference. 5. Once Section 7 is removed, approve under standard delegation of authority and sign. 6. Until it's signed, tell the team not to share technical materials with Halvard. *This is a screening analysis, not legal advice. Counsel should review before you rely on it.*
without
**Short answer:** Section 7 should stop you until someone makes a call on it. The rest is fixable with quick redlines and shouldn't hold up the deep dive if the other side is reasonable. ## Should stop signing as-is **Section 7 ("General Cooperation") is a no-hire clause, not a cooperation clause.** - The heading is misleading. It bars both soliciting *and hiring* employees, directly or indirectly. - It runs for the 2-year term plus 24 months, so up to **4 years**. - It has no carve-out for general job postings, for people who apply on their own, or for people who have left the company. - "Employees with whom it had contact" is vague. A single email or a single call could be enough. - A no-hire can raise antitrust (no-poach) concerns. It can also be unenforceable for employees in states like California, which creates uncertainty for you. - Recruiting and HR should weigh in, because this is a business restriction, not confidentiality protection. **Fix:** Delete it, since an NDA doesn't need it. If Halvard insists, narrow it to a non-solicit only, 12 months, with a carve-out for general solicitations and for people who respond to them or who have left. ## Should fix, but not deal-breakers 1. **Section 3(e) is drafted wrong.** Legally compelled disclosure is listed as an exclusion from the definition of Confidential Information. Read literally, once information is subject to a legal disclosure requirement, it stops being confidential at all. It should be a separate clause that permits disclosure only to the extent required, with notice and cooperation to seek a protective order. 2. **No trade-secret survival.** Obligations end 5 years after signing (2-year term plus 3 years). For a technical deep dive, source code, architecture, and models should stay protected for as long as they remain trade secrets. 3. **Retained copies (Section 6).** Backup copies are exempt from return or destruction, but nothing says they stay confidential and unused. Add that. 4. **Missing
Show the rest (14 more lines)
standard protections:** - no license or IP transfer - no obligation to do a deal - information provided "as is" - no reverse engineering - the recipient is responsible for breaches by its contractors and advisors - injunctive relief 5. **Section 8.** "Courts of Delaware" doesn't say whether the venue is exclusive. Halvard is a "Ltd.", probably foreign, so consider making it exclusive and confirming how you'd enforce a judgment. ## Quick checks - Confirm Halvard's jurisdiction and that the signatory has authority. - Even with a signed NDA, stage the deep dive. Share only what the integration evaluation needs, and hold back core IP like source code and proprietary models until there is a deeper agreement. I'm not a substitute for your counsel. Since this is a same-day turnaround, send Legal the Section 7 and 3(e) issues first. Those two redlines are small and can be turned around quickly.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
clean-standard-nda

“Quick sanity check before I sign this NDA with a design agency we might hire. Anything blocking?”

exclusivity-in-disguise

“A supplier sent this 'confidentiality agreement' before they'll quote on our packaging order. Can our ops manager just sign it?”

hidden-non-solicit

“Sales wants to sign this mutual NDA with a prospect today so we can start a technical deep dive. Anything that should stop us?”

residuals-perpetual-penalty

“Can you triage this NDA from a potential acquirer of one of our product lines? I need to know whether it can go straight to signature.”

wrong-direction-one-way

“We're about to share our product roadmap and pricing model with a reseller. They sent us their NDA. Is it OK to sign?”

Install

Download the .zip and unzip it. Put its files, in a folder named triage-nda, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.