triage-nda
Skill1 starsChanged 7 months agoMITView on GitHub
Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Screens for embedded non-competes, non-solicits, and non-standard terms. Trigger with "triage this NDA", "NDA review", "screen this NDA", "classify NDA", or "check this NDA".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- anthropics/knowledge-work-plugins★ 36ksame name
- alebgl77/claude-inc★ 21same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Check every section for: non-compete, non-solicitation, exclusivity, standstill, and non-circumvention clauses.
- Distinctive: line 87
Check every section for restrictive covenants, not just obviously labeled ones.
- Distinctive: line 88
Verify all four standard exclusions are present.
- Distinctive: line 92
When triaging multiple NDAs, process GREEN first to clear the queue.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
NDA Triage
Rapidly screen incoming NDAs using a traffic-light classification framework. Flag deviations and embedded restrictive covenants.
Workflow
Step 1: Extract NDA Basics
Parties, direction (one-way/mutual), permitted purpose, term, governing law, and template origin (our paper, counterparty, third-party).
Step 2: Screen for Restrictive Covenants
Check every section for: non-compete, non-solicitation, exclusivity, standstill, and non-circumvention clauses. If any found, automatically classify YELLOW or RED.
Step 3: Check Key Terms
| Term | Standard | Flag if |
| Definition of CI | Marked or identified | Overly broad / "all information" |
| Exclusions | Public, independent, prior, court order | Any standard exclusion missing |
| Term | 2-3 years | >5 years or perpetual |
| Return/destroy | On request | No obligation |
| Residuals | Not required | Absent when needed |
| Governing law | Preferred jurisdiction | Unfavorable foreign jurisdiction |
Step 4: Classify
- GREEN: Standard terms, no covenants, minor deviations. Approve with standard delegation.
- YELLOW: Non-standard terms needing counsel review (embedded non-solicitation, >5yr term, missing exclusions, one-sided obligations).
- RED: Full legal review required (embedded non-compete, exclusivity, standstill, perpetual term, IP assignment, high-risk jurisdiction).
Output Format
## NDA Triage Report
**Counterparty**: [Name] | **Date**: [YYYY-MM-DD]
**Classification**: [GREEN / YELLOW / RED]
**Direction**: [Mutual / One-way]
### Restrictive Covenant Screen
| Covenant | Present | Section | Severity |
|----------|---------|---------|----------|
| Non-compete | No | -- | -- |
| Non-solicitation | YES | 4.2 | YELLOW |
### Key Terms
| Term | Contract Position | Standard | Status |
|------|------------------|----------|--------|
| Definition | All information | Marked | FLAG |
| Term | 3 years | 2-3 yrs | OK |
### Recommended Action
[GREEN: Approve / YELLOW: Route to counsel / RED: Route to senior counsel]Examples
User: "Triage this NDA from TechCo for a potential partnership" Action: Extract terms, screen for covenants, compare against standards. Standard mutual NDA with no covenants classifies GREEN. If it contains a non-solicitation, classify YELLOW.
User: "We have five NDAs to sign this week -- prioritize them" Action: Triage each NDA, classify GREEN/YELLOW/RED, rank by review urgency. GREEN proceeds immediately; YELLOW and RED need counsel.
Best Practices
- Check every section for restrictive covenants, not just obviously labeled ones. Non-competes hide in definitions and miscellaneous clauses.
- Verify all four standard exclusions are present.
- For international NDAs, flag governing law requiring foreign litigation.
- Residuals clauses matter when your engineers will be exposed to technical information.
- Track NDA expiration dates and set reminders for return/destroy obligations.
- When triaging multiple NDAs, process GREEN first to clear the queue.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

