If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontriage-ndaExecute the skills CLI command in your project's root directory to begin installation:
Fetches triage-nda from anthropics/knowledge-work-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate triage-nda. Access via /triage-nda in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Triage the NDA: @$1
Rapidly triage incoming NDAs against standard screening criteria. Classify the NDA for routing: standard approval, counsel review, or full legal review.
Important: You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
/triage-nda
Accept the NDA in any format:
If no NDA is provided, prompt the user to supply one.
Look for NDA screening criteria in local settings (e.g., legal.local.md).
The NDA playbook should define:
If no NDA playbook is configured:
Evaluate the NDA against each screening criterion systematically.
All of the following carveouts should be present:
Based on the screening results, assign a classification:
All of the following must be true:
Routing: Approve via standard delegation of authority. No counsel review required.
One or more of the following are present, but the NDA is not fundamentally problematic:
Routing: Flag specific issues for counsel review. Counsel can likely resolve with minor redlines in a single review pass.
One or more of the following are present:
Routing: Full legal review required. Do not sign. Requires negotiation, counterproposal with the organization's standard form NDA, or rejection.
Output a structured report:
## NDA Triage Report
**Classification**: [GREEN / YELLOW / RED]
**Parties**: [party names]
**Type**: [Mutual / Unilateral (disclosing) / Unilateral (receiving)]
**Term**: [duration]
**Governing Law**: [jurisdiction]
**Review Basis**: [Playbook / Default Standards]
## Screening Results
| Criterion | Status | Notes |
|-----------|--------|-------|
| Mutual Obligations | [PASS/FLAG/FAIL] | [details] |
| Definition Scope | [PASS/FLAG/FAIL] | [details] |
| Term | [PASS/FLAG/FAIL] | [details] |
| Standard Carveouts | [PASS/FLAG/FAIL] | [details] |
| [etc.] | | |
## Issues Found
### [Issue 1 -- YELLOW/RED]
**What**: [description]
**Risk**: [what could go wrong]
**Suggested Fix**: [specific language or approach]
[Repeat for each issue]
## Recommendation
[Specific next step: approve, send for review with specific notes, or reject/counter]
## Next Steps
1. [Action item 1]
2. [Action item 2]
Based on the classification, recommend the appropriate next step:
| Classification | Recommended Action | Typical Timeline |
|---|---|---|
| GREEN | Approve and route for signature per delegation of authority | Same day |
| YELLOW | Send to designated reviewer with specific issues flagged | 1-2 business days |
| RED | Engage counsel for full review; prepare counterproposal or standard form | 3-5 business days |
For YELLOW and RED classifications:
Standard position: Confidential information should be limited to non-public information disclosed in connection with the stated purpose, with clear exclusions. Redline approach: Narrow the definition to information that is marked or identified as confidential, or that a reasonable person would understand to be confidential given the nature of the information and circumstances of disclosure.
Standard position: Must include a carveout for information independently developed without reference to or use of the disclosing party's confidential information. Risk if missing: Could create claims that internally-developed products or features were derived from the counterparty's confidential information. Redline approach: Add standard independent development carveout.
Standard position: Non-solicitation provisions do not belong in NDAs. They are appropriate in employment agreements, M&A agreements, or specific commercial agreements. Redline approach: Delete the provision entirely. If the counterparty insists, limit to targeted solicitation (not general recruitment) and set a short term (12 months).
Standard position: Resist residuals clauses. If required, limit to: (a) general ideas, concepts, know-how, or techniques retained in the unaided memory of individuals who had authorized access; (b) explicitly exclude trade secrets and patentable information; (c) does not grant any IP license. Risk if too broad: Effectively grants a license to use the disclosing party's confidential information for any purpose.
Standard position: 2-5 years from disclosure or termination, whichever is later. Trade secrets may warrant protection for as long as they remain trade secrets. Redline approach: Replace perpetual obligation with a defined term. Offer a trade secret carveout for longer protection of qualifying information.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
triage-nda is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
triage-nda has been reliable in day-to-day use. Documentation quality is above average for community skills.
triage-nda fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: triage-nda is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added triage-nda from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in triage-nda — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
triage-nda reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend triage-nda for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
triage-nda reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added triage-nda from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 49