amendment-history

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

Quality

88%

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

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 well-structured, highly actionable legal workflow with clear sequencing and built-in validation checkpoints. Its main weaknesses are a monolithic single-file structure with no progressive disclosure to separate references, and a few prose passages that could be trimmed.

Suggestions

Trim the narrative Purpose paragraph to a single sentence or remove it; the Instructions and mode-detection sections already convey the skill's intent without motivational framing.

Move the large Mode 1 and Mode 2 output-format templates into reference files under references/ (e.g., summary-output.md and provision-trace-output.md) and link to them from SKILL.md to improve progressive disclosure.

Tighten the 'What this skill does not do' section into a compact bulleted list to reduce prose and token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the narrative Purpose paragraph ('Contracts accumulate amendments. By the third amendment, nobody remembers...') and some prose framing could be tightened, so it does not reach 'every token earns its place'.	2 / 3
Actionability	Provides concrete, copy-ready guidance — full output-format templates with placeholders, mode-detection trigger phrases, provision mappings, and ordering rules with specific filename patterns — which for an instruction-only skill counts as fully actionable.	3 / 3
Workflow Clarity	Clear sequenced workflow (Step 1 load/order → Step 2 read/index → Mode 1/2 output) with explicit checkpoints: confirm ordering only when uncertain, flag party mismatches, build an index before producing output, and a watch-items review.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~290-line monolithic document with well-organized sections but no file-level split; the large inline Mode 1/Mode 2 output templates are content that could live in separate reference files.	2 / 3
	Total	10 / 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.

A strong, third-person description that states concrete capabilities and pairs them with explicit, natural-language trigger phrases. It cleanly answers both what the skill does and when to use it within a distinct legal niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'a summary of all changes over time, or a provision trace for a specific clause' — matching the anchor for naming several specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (trace contract changes / summary / provision trace) and 'when' via a clear 'Use when the user says...' trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Quoted natural user phrases — "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved" — give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a distinct legal niche — amendment history across base agreement and amendments — with specific 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/amendment-history/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.