CtrlK
BlogDocsLog inGet started
Tessl Logo

contract-comparison

Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%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 content is highly actionable with a concrete workflow, clear change taxonomy, and a complete output template. It loses points for lacking an explicit verification step in the workflow and for keeping a large template inline rather than splitting it into a referenced file.

Suggestions

Add an explicit verification step before output generation, e.g. 'Verify every section from both documents appears in the comparison and that the change-count totals reconcile.'

Move the full CONTRACT-COMPARISON.md output template into a referenced template file (e.g. references/OUTPUT_TEMPLATE.md) and summarize its structure inline to reduce monolithic bulk.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of basic-concept padding, but the role preamble ('You are an AI Legal Analyst...') and the large fully-embedded output template could be tightened.

2 / 3

Actionability

Provides highly concrete, copy-paste-ready guidance: explicit change-type taxonomy, a dangerous-pattern checklist, and a complete markdown output template with exact instructions to quote source text.

3 / 3

Workflow Clarity

Five steps are clearly sequenced, but there is no explicit validation or verification checkpoint (e.g., confirm every section was compared or that the change totals reconcile), so checkpoints are only implicit.

2 / 3

Progressive Disclosure

A single well-organized file with no nested references, but it is monolithic with a large inline output template that could reasonably be split into a separate reference file.

2 / 3

Total

9

/

12

Passed

Description

67%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 specific and distinct, naming several concrete comparison/analysis actions within a clear contract-comparison niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause and somewhat technical phrasing over natural user terms.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when comparing two contract versions or two different contracts, redlining changes, or assessing who a contract favors.'

Replace jargony phrases like 'favorability analysis' with natural terms a user would say, such as 'see who each change favors' or 'compare contracts'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'comparison', 'change tracking', 'favorability analysis', and 'risk assessment' — matching the anchor for naming several specific concrete actions.

3 / 3

Completeness

Clearly states what the skill does but has no 'Use when...' or equivalent trigger clause, so the 'when' is only implied — capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('contract versions', 'two different contracts', 'comparison') but leans technical with 'favorability analysis'/'risk assessment' and omits common variations like 'compare contracts', 'redline', or 'diff'.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (side-by-side contract comparison) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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