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.

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

Source material given with the request

NON-DISCLOSURE AGREEMENT Between Brightwater Channel Partners LLC ("Discloser") and Calloway Software, Inc. ("Recipient"). 1. Recipient agrees to hold in confidence all information of any kind disclosed by Discloser, whether oral or written and whether or not marked as confidential ("Confidential Information"). 2. Exclusions. Confidential Information does not include information that is publicly available through no fault of Recipient. 3. Recipient may disclose Confidential Information only to its employees who need to know it. 4. Term. Recipient's obligations last three (3) years from the date of each disclosure. 5. Governing law: State of New York. (Calloway Software is our company.)
with the skill
## NDA Triage Report **Classification**: 🔴 **RED. Do not sign, and do not share the roadmap or pricing yet.** **Parties**: Brightwater Channel Partners LLC (Discloser) and Calloway Software, Inc. (Recipient, i.e., us) **Type**: Unilateral, with us as the *receiving* party **Term**: Obligations last 3 years from each disclosure **Governing Law**: New York **Review Basis**: Default market-standard criteria (no NDA playbook configured) ### The main problem This NDA protects the wrong party. Only Calloway, as Recipient, has any confidentiality obligations. Brightwater has none. If you share your product roadmap and pricing model under this document, **Brightwater could share or use them freely.** Meanwhile, we would be bound to protect anything they send us, with very broad obligations. ### Screening Results | Criterion | Status | Notes | |---|---|---| | Mutual obligations | **FAIL** | Unilateral, in the wrong direction for our planned disclosure | | Definition scope | **FAIL** | "All information of any kind… whether or not marked" is overbroad and has no purpose limitation | | Standard carveouts | **FAIL** | Only "publicly available" is present. Missing prior possession, independent development, third-party receipt, and legal compulsion | | Permitted disclosures | **FLAG** | Employees only. No contractors, advisors, affiliates, or legally required disclosures |
Show the rest (38 more lines)
| Term | **FLAG** | 3 years from each disclosure is within range, but there is no overall agreement term, and there is no longer protection for trade secrets (relevant to pricing and roadmap) | | Use restriction / standard of care | **FLAG** | Neither is stated. This is a gap if we are the discloser | | Return/destruction | **FLAG** | Absent | | Remedies | **FLAG** | Absent (no injunctive relief acknowledgment, which would matter to us as discloser) | | Problematic provisions | **PASS** | No non-solicit, non-compete, exclusivity, residuals, IP license, or audit rights | | Governing law | **PASS/FLAG** | New York is acceptable, but there is no venue or jurisdiction clause | ### Issues Found **1. Wrong direction (RED)** - **Risk**: Our roadmap and pricing are unprotected, and Brightwater could disclose them to competitors or customers. - **Fix**: Replace with a *mutual* NDA, ideally our standard form. Alternatively, have Brightwater revise the parties' roles so both are "Disclosing" and "Receiving" parties. **2. Overbroad definition (RED)** - **Risk**: Everything Brightwater says or sends us, marked or not, becomes confidential, including things we already know or that are trivial. - **Fix**: Limit to non-public information disclosed for a defined purpose (e.g., evaluating a reseller relationship) that is marked or that a reasonable person would understand to be confidential. Allow written confirmation within 30 days for oral disclosures. **3. Missing carveouts (RED)** - **Risk**: Without independent development, we could face claims that our own products or features derive from their information. Without legal compulsion, we would be in breach if we complied with a subpoena. - **Fix**: Add all four missing carveouts: prior possession, independent development, third-party receipt, and legal compulsion (with notice where permitted). **4. Narrow permitted disclosures (YELLOW)** - **Risk**: We could not involve outside counsel, accountants, contractors, or affiliates. - **Fix**: Extend to employees, affiliates, contractors, and professional advisors with a need to know who are bound by similar obligations. **5. Missing structural terms (YELLOW)** - Add a defined purpose and use restriction, a standard of care, return/destruction with a retention exception, an injunctive relief clause (mutual), venue/jurisdiction, and a longer protection period for trade secrets. ### Recommendation Do not sign as drafted. Send Brightwater **our standard mutual NDA** as a counterproposal. If they insist on their paper, ask for the revisions above, particularly mutuality, the narrowed definition, and the full carveout set. Because this is RED, route it to counsel for full review. ### Next Steps 1. **Hold the roadmap and pricing materials** until a signed NDA is in place. Don't share them informally in the meantime. 2. Send our standard mutual NDA to Brightwater, or send counsel's redlines to theirs. 3. Escalate to legal/counsel (3-5 business days typical). Give them this summary and flag that the roadmap and pricing share is the business driver. 4. Once signed, consider marking shared materials "Confidential" as good practice. *This is a screening aid, not legal advice. Qualified counsel should review before you rely on it or sign anything. If you have an NDA playbook or standard form, share it and I can re-run the triage against your criteria.*
without
**Not as written.** The biggest problem is that the NDA protects the wrong party. ## Critical issue: it's one-way, and in the wrong direction Brightwater is the only "Discloser" and Calloway is the only "Recipient." Your roadmap and pricing would be shared *with* Brightwater, and nothing in this agreement obligates them to keep it confidential. You'd be bound to protect their information while your most sensitive information goes out unprotected. **Fix:** Make it mutual, so each party is both Discloser and Recipient, or have them sign your own NDA template. Don't share anything until a protective agreement is signed. ## Other issues (these matter even if it's made mutual) | Clause | Problem | Suggested fix | |---|---|---| | **1. Definition** | Covers "all information of any kind," marked or not. This is overbroad and creates compliance risk for you as a recipient, since you can't tell what's covered. | Limit it to information that is marked confidential, or that a reasonable person would understand to be confidential. | | **2. Exclusions** | Only covers public information. It's missing standard carve-outs. | Add exclusions for information that was already known to the recipient, was independently developed, or was rightfully received from a third party. | | **3. Permitted disclosure** | Employees only. You couldn't share with attorneys, accountants, contractors, or affiliates, even where legitimately needed. | Add "employees, contractors, and professional advisors with a need to know who are bound by confidentiality obligations." | | **4. Term** | Obligations expire 3 years after each disclosure. Roadmap and pricing may be fine at 3 years, but trade secrets (source code, algorithms) would lose protection. | Keep 3 years for general information, but protect trade secrets for as long as they remain trade secrets. | | **Missing** | No compelled-disclosure carve-out (subpoenas, court orders). No return or destruction of materials. No "use only for evaluating the
Show the rest (10 more lines)
business relationship" restriction. No remedies clause (e.g., injunctive relief). | Add all four. The use restriction is especially important for you as the discloser. | | **5. Governing law** | New York law is workable, but there's no venue or dispute clause. | Optional: specify venue. Check whether you're comfortable litigating in New York. | ## Practical suggestions - **Hold the information** until the signed NDA is in place. - **Share in stages.** Even with an NDA, consider giving the reseller only what they need. Pricing models and a detailed roadmap are among the most sensitive things to share. - **Check whether this NDA is the only agreement.** A reseller agreement may later supersede it, so make sure the two don't conflict. - **Have counsel review the final version.** This is a general analysis, not legal advice, and an attorney can quickly turn this around into a mutual form. I can draft a redline or a short mutual NDA based on these points if you'd like.

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.