amendment-history Skill
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] ev Published by anthropics in claude-for-legal.
What is amendment-history Skill?
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] ev Published by anthropics in claude-for-legal. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using claude-for-legal
Technical details
- Install or run with Copy skill directory
When to use amendment-history Skill
- Use it for developers using claude-for-legal.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-for-legal
- Skill file: commercial-legal/skills/amendment-history/SKILL.md
What it does
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] ev
Skill instructions
/amendment-history Loads a base agreement and all amendments, then either summarizes what changed over time or traces a specific provision to its current controlling language. Instructions 1. Get the documents: From file upload, [CLM ID (coming soon)], or [repository link (coming soon)]. Accept multiple files in one invocation. If none provided, ask. 2. Detect the mode by parsing the request per the mode detection rules below. If a provision name is clearly stated, go straight to Mode 2. If no provision is mentioned, run Mode 1. Ask only if genuinely ambiguous. 3. Run the workflow below. Follow it fully. 4. Offer follow-ups after output: - "Want me to trace another provision?" - "Want a full playbook review of the current agreement as amended?" (routes to vendor-agreement-review) - "Want a stakeholder summary of the key changes?" (routes to stakeholder-summary) Examples /commercial-legal:amendment-history acme-msa.pdf amendment-1.pdf amendment-2.pdf /commercial-legal:amendment-history
Explore related resources
Frequently asked questions
What is amendment-history?
amendment-history is a open-source AI agent skill with Copy skill directory. 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.
Who is amendment-history best for?
amendment-history is best for reusing agent instructions, scripts, and references.
How do I install amendment-history?
Install or run amendment-history using Copy skill directory. Check amendment-history for the latest setup command.
Is amendment-history actively maintained?
amendment-history may need a closer maintenance check before production use.
Auto-fetched from GitHub.
