Localized reading guide
triage-ndaPurpose, usage and source
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.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
legal/skills/triage-nda/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill 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.
How the upstream workflow works
Step 1: Accept the NDA
Accept the NDA in any format: File upload: PDF, DOCX, or other document format URL: Link to the NDA in a document system Pasted text: NDA text pasted directly
Upstream passage · L25 ↗Step 2: Load NDA Playbook
Look for NDA screening criteria in local settings (e.g., legal.local.md). The NDA playbook should define: Mutual vs. unilateral requirements Acceptable term lengths
Step 3: Quick Screen
Evaluate the NDA against each screening criterion systematically.
Upstream passage · L56 ↗/triage-ndaRequirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- /triage-nda -- NDA Pre-Screening
- Step 1: Accept the NDA
- Step 2: Load NDA Playbook
- Step 3: Quick Screen
- 1. Agreement Structure
- 2. Definition of Confidential Information
- 3. Obligations of Receiving Party
- 4. Standard Carveouts
- 5. Permitted Disclosures
- 6. Term and Duration
- 7. Return and Destruction
- 8. Remedies
- 9. Problematic Provisions to Flag
- 10. Governing Law and Jurisdiction
- Step 4: Classify
- GREEN -- Standard Approval
- YELLOW -- Counsel Review Needed
- RED -- Significant Issues
- Step 5: Generate Triage Report
- Step 6: Routing Suggestion
- Issue: Overbroad Definition of Confidential Information
- Issue: Missing Independent Development Carveout
- Issue: Non-Solicitation of Employees
- Issue: Broad Residuals Clause
- Issue: Perpetual Confidentiality Obligation
- Notes
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
767a8f6759268e003ee882af8dfb56579aca2121b9dc49a2c65c4e77de93f768