review

Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

85%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 a well-sequenced, actionable routing workflow with clear checkpoints and concrete templates. Its only weakness is repetition of the long config path and the confirm_routing default across multiple sections.

Suggestions

Define the config path once (e.g., 'the commercial-legal CLAUDE.md' with the full path stated once) and refer to it by short name thereafter to cut repeated tokens.

Consolidate the confirm_routing default explanation into one place rather than restating it in step 1, step 5, and the Configuring section.

Consider a short note that routing to vendor-agreement-review / nda-review / saas-msa-review delegates the detailed playbook checks, so the body does not need to re-summarize what those skills do.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the long path '~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md' repeats ~6 times and the confirm_routing default is re-explained in step 1, step 5, and the Configuring section — it could be tightened.	2 / 3
Actionability	Provides a concrete title→skill routing table, an exact confirmation-dialog template with placeholders, and a specific follow-up list — copy-paste-ready, actionable guidance.	3 / 3
Workflow Clarity	An 8-step sequence with explicit checkpoints: stop if placeholders present, wait for user confirmation, fallback (read two pages) on ambiguity, and an escalation check — with a feedback loop when the user corrects routing.	3 / 3
Progressive Disclosure	No bundle files are provided or needed (it is a meta-skill routing to other skills); the single body is organized into clear sections with no nested references, which fits the well-organized single-file case.	3 / 3
	Total	11 / 12 Passed

Description

100%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 is strong: it states concrete actions, supplies natural trigger phrases, explicitly pairs 'what' with 'when', and carves out a distinct niche. It is concise without padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Review a vendor agreement, NDA, or SaaS subscription', 'Identifies the agreement structure from titles', 'routes to the right review skill', 'integrates the output into a single memo' — matching the 'Lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (review/identify/route/integrate) and when via a 'Use when the user says…' clause with concrete triggers, matching the top anchor.	3 / 3
Trigger Term Quality	Includes natural phrasings users would say — 'review this contract', 'check this MSA', 'is this NDA okay', 'look at this SaaS agreement' — giving good coverage of real-world trigger terms.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — inbound agreement review against a playbook routing to named downstream skills — with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: anthropics/claude-for-legal
Path: commercial-legal/skills/review/SKILL.md
Commit: 4a6c651

Reviewed: 6 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.