custom-nda-generator

Generates a complete, customized Non-Disclosure Agreement with plain English annotations, tailored to the specific parties and situation

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/legal-nda/SKILL.md

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.

The body is highly actionable with a clear sequenced workflow, concrete template, and sensible defaults. Its main weaknesses are redundancy between the Step 2 section descriptions and the Step 4 template, and a monolithic structure that could offload the template into a reference file.

Suggestions

Consolidate the Step 2 section descriptions and the Step 4 template into a single authoritative structure to remove the duplicated section list.

Move the full NDA output template into a reference file (e.g., references/nda-template.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Add a brief final verification step (e.g., confirm all 15 required sections and a plain-English annotation are present) to close the workflow with an explicit output check.

Dimension	Reasoning	Score
Conciseness	The body is largely necessary domain content and avoids explaining basics Claude knows, but the Step 2 section-by-section descriptions duplicate the Step 4 output template (same sections restated with "[clause]"/"[Annotation]" placeholders), which could be consolidated; this fits level 2's "mostly efficient but could be tightened."	2 / 3
Actionability	It provides a concrete output template, file-naming convention (NDA-[Party1]-[Party2]-[date].md), specific defaults (2-year term, 3/5-year survival), a fixed annotation block format, and per-section content guidance — actionable, specific instruction rather than vague direction, matching level 3 for an instruction-only skill.	3 / 3
Workflow Clarity	The four steps are clearly sequenced with explicit gating checkpoints ("ask the user before proceeding" for missing critical info; "ask before generating" for jurisdiction) and a checklist of 15 required sections plus required/optional info, satisfying level 3's clear sequence with checkpoints; no destructive/batch operation cap applies.	3 / 3
Progressive Disclosure	The skill is a well-sectioned single SKILL.md but is a monolithic ~280-line document with no bundle files, and the full output template (content that could live in a separate reference file) is inline, matching level 2's "content that should be separate is inline."	2 / 3
	Total	10 / 12 Passed

Description

57%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.

The description clearly conveys the skill's purpose and occupies a distinct niche, but it lacks explicit "when to use" trigger guidance and omits common natural terms like "NDA" and "confidentiality agreement." Adding a Use-when clause and the abbreviation would lift specificity and completeness.

Suggestions

Add a "Use when…" clause naming natural triggers, e.g. "Use when the user needs to draft an NDA, non-disclosure agreement, or confidentiality agreement."

Include the "NDA" abbreviation and "confidentiality agreement" as natural trigger terms a user would actually say.

Optionally enumerate concrete actions (e.g., draft, annotate, tailor to mutual/one-way variants) to push specificity toward level 3.

Dimension	Reasoning	Score
Specificity	"Generates a complete, customized Non-Disclosure Agreement with plain English annotations, tailored to the specific parties and situation" names the domain and key features (annotations, tailoring) but centers on a single action rather than listing multiple concrete actions, matching the level-2 anchor and falling short of level 3's "multiple specific concrete actions."	2 / 3
Completeness	The description clearly states what the skill does but provides no "Use when…" clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes "Non-Disclosure Agreement" but omits common natural variants a user would say ("NDA", "confidentiality agreement"), fitting the level-2 anchor of relevant keywords missing common variations rather than the broad level-3 coverage.	2 / 3
Distinctiveness Conflict Risk	NDA generation is a clear, narrow niche unlikely to overlap with other skills, matching the level-3 anchor of a distinct niche with low conflict risk.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: zubair-trabzada/ai-legal-claude
Path: skills/legal-nda/SKILL.md
Commit: 19ece98

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.