CtrlK
BlogDocsLog inGet started
Tessl Logo

nda-review

Reference: fast triage of inbound NDAs into GREEN / YELLOW / RED so the team only spends lawyer time on the ones that need it. Built for sales and BD to self-serve before pinging legal. Loaded by /commercial-legal:review when an NDA is detected.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./commercial-legal/skills/nda-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-gated legal triage workflow with concrete templates and checklists. Its main weaknesses are token inefficiency from the repeated long config path and a monolithic structure with no progressive disclosure into bundle files.

Suggestions

Define the recurring CLAUDE.md path once (e.g., as a short alias or variable) and refer to it thereafter, instead of repeating the full path ~20 times.

Split the detailed check reference and/or the GREEN/YELLOW/RED output templates into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is substantive (no condescending explanation of basic legal concepts), but it is padded by the full path ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md repeated ~20 times and some wordy justifying prose that could be tightened.

2 / 3

Actionability

Guidance is concrete and copy-paste ready: full GREEN/YELLOW/RED output templates with exact fields, an enumerated five-carveout checklist, and a verbatim one-way-NDA questionnaire with numbered questions.

3 / 3

Workflow Clarity

The flow is clearly sequenced (matter context → destination check → side determination → scope check → triage) with explicit gates such as the attorney-reviewed-playbook check before GREEN and the "do not proceed without an explicit yes" signature gate, plus a feedback loop when the playbook is silent.

3 / 3

Progressive Disclosure

Sections are well-organized with headers, but the skill ships no bundle files and is a ~300-line monolithic document; material like the detailed check reference and the three output templates could live in separate one-level-deep files.

2 / 3

Total

10

/

12

Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A focused, distinct description that clearly answers what it does and when it activates, with a concrete triage action. It is held back from the top by listing only one action and by thin trigger-term coverage.

Suggestions

Add common trigger-term variations such as "non-disclosure agreement" or "confidentiality agreement" alongside "NDA".

Name one or two more concrete actions (e.g., "flags non-NDA provisions, generates a triage memo") to broaden the specificity beyond a single triage step.

DimensionReasoningScore

Specificity

The description names a concrete action ("fast triage of inbound NDAs into GREEN / YELLOW / RED") and the domain, but it lists a single triage action rather than the multiple concrete actions the top anchor expects.

2 / 3

Completeness

It states what the skill does ("fast triage of inbound NDAs into GREEN / YELLOW / RED") and gives an explicit trigger ("Loaded by /commercial-legal:review when an NDA is detected"), answering both what and when.

3 / 3

Trigger Term Quality

"NDA" is a natural keyword a user would say ("inbound NDAs", "when an NDA is detected"), but coverage is thin — common variations like "non-disclosure agreement" or "confidentiality agreement" are absent.

2 / 3

Distinctiveness Conflict Risk

"fast triage of inbound NDAs into GREEN / YELLOW / RED" with an NDA-detection trigger carves a clear niche that is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/claude-for-legal
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.