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 — Full legal review required. Do not sign as drafted.** The central problem is that **this NDA protects the reseller’s information, not yours**. Brightwater is the “Discloser,” and Calloway is the “Recipient.” Nothing in the supplied text obligates Brightwater to protect your product roadmap or pricing model. **Parties:** Brightwater Channel Partners LLC and Calloway Software, Inc. **Type:** Unilateral; Calloway is the receiving party—wrong direction for your planned disclosures **Term:** Confidentiality obligations last three years from each disclosure; no separate agreement term stated **Governing law:** New York **Review basis:** Default screening standards; no company playbook was provided ## Screening Results | Criterion | Status | Notes | |---|---|---| | Appropriate obligations | **FAIL** | Brightwater has no confidentiality obligations for Calloway’s disclosures. | | Definition scope | **FAIL** | “All information of any kind” is overly broad and lacks a purpose-related limitation. | | Standard carveouts | **FAIL** | Only public availability is excluded. Prior possession, independent development, rightful third-party receipt, and legally compelled disclosure protections are missing. | | Use restriction | **FAIL** | No express restriction limiting use to evaluating or conducting the reseller relationship. |
Show the rest (36 more lines)
| Standard of care | **FLAG** | “Hold in confidence” does not specify a reasonable-care standard. | | Permitted disclosures | **FLAG** | Employees only; no permission for contractors, counsel, accountants, or other advisors. | | Duration | **PASS** | Three years per disclosure is within the default standard range. | | Return/destruction | **FLAG** | No return/destruction requirement or legal, compliance, and backup retention exceptions. | | Remedies and restrictive provisions | **PASS** | No liquidated damages, non-compete, non-solicitation, residuals, IP grant, or audit provisions appear in the supplied text. | | Governing law | **PASS** | New York is a reasonable commercial jurisdiction; forum is unspecified. | ## Key Issues and Suggested Fixes ### 1. Wrong-direction protection — RED **Risk:** Your roadmap and pricing model would not be protected by this NDA when shared with Brightwater. **Suggested fix:** Use a mutual NDA if both parties will disclose information. If only Calloway will disclose, make Calloway the discloser and Brightwater the recipient. **Simply swapping the labels would not resolve the other issues below.** ### 2. Missing critical carveouts — RED **Risk:** Calloway could face confidentiality claims involving information it already knew, developed independently, or lawfully obtained elsewhere. The agreement also lacks express permission for legally required disclosures. **Suggested fix:** Add exclusions for prior knowledge, independent development without use of confidential information, and lawful third-party receipt. Permit legally compelled disclosures, with advance notice where legally permitted. ### 3. Overbroad scope and no express use limitation — RED **Risk:** Calloway takes on broad obligations for Brightwater’s information, while the document does not expressly prohibit using confidential information outside the reseller discussions. **Suggested fix:** Define confidential information as nonpublic information disclosed for a stated reseller-evaluation purpose that is marked confidential or reasonably understood to be confidential. Restrict use to that purpose. ### 4. Operational gaps — YELLOW **Suggested fix:** Permit need-to-know disclosures to advisors and contractors subject to confidentiality duties; specify reasonable care; and add return/destruction provisions with appropriate retention exceptions. ## Recommendation and Next Steps 1. **Hold off on signing and sharing your roadmap or pricing model** until an appropriate NDA is executed. 2. Send this to **Calloway’s legal counsel for full review**, highlighting the wrong-direction protection and missing carveouts. 3. Preferably counter with **Calloway’s standard mutual NDA**, if available, rather than patching this short form. **Reviewer summary:** Reseller’s NDA binds only Calloway, leaves Calloway’s planned disclosures unprotected, omits critical carveouts, and lacks an express purpose/use restriction. *This is a preliminary legal-workflow screening, not legal advice. Qualified counsel should review the agreement before you rely on it.*
without
**I would not sign this as written for your intended purpose.** The main problem is that it protects the reseller’s information—not yours. Calloway is defined as the **“Recipient,”** and Brightwater as the **“Discloser.”** Only Calloway takes on confidentiality obligations. If you share your product roadmap and pricing model, this NDA does **not expressly require Brightwater to keep them confidential or restrict its use of them.** Before sharing, ask for a **mutual NDA** if both sides will disclose information, or reverse the roles if only Calloway will disclose. Other changes worth requesting: | Issue | Why it matters / suggested change | |---|---| | **No restriction on use** | Confidentiality alone is not enough. Limit use to evaluating and negotiating the proposed reseller relationship—not competing, developing products, or other purposes. | | **Overbroad definition** | “All information of any kind” could impose obligations on Calloway for routine, nonconfidential exchanges. Cover information identified as confidential or reasonably understood to be confidential from its nature and circumstances. | | **Missing standard exclusions** | Add information already lawfully known, independently developed without using confidential information, or lawfully received from a third party without confidentiality restrictions. | | **Employees only** | This could prevent Calloway from sharing Brightwater’s information with outside lawyers, accountants, or other necessary advisers. Permit appropriate representatives subject to confidentiality duties. | | **No legally required disclosure exception** | Permit disclosures required by law, regulation, or court order, with notice where legally permitted and reasonable protective steps. | | **Three-year protection** | Three years may suit some commercial information, but consider longer protection for sensitive pricing and trade-secret protection for as long as the information qualifies as a trade secret. | | **No return/deletion
Show the rest (9 more lines)
provision** | Add return or destruction on request or at the end of discussions, with reasonable exceptions for legal retention and backups. | New York governing law is not inherently a problem, but counsel should confirm that it is acceptable for your company. **Practical next step:** Hold off on sending the roadmap or pricing until the correct NDA is signed. You could respond: > “Thanks for sending this. The current draft protects Brightwater’s disclosures only. Since Calloway will be sharing confidential product roadmap and pricing information, please send a mutual NDA covering both parties, including a restriction limiting use to evaluating the proposed reseller relationship.” This is a contract issue-spotting review, not a legal opinion; have your lawyer approve the revised agreement before signing.

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.