contract-comparison
Skill0 starsChanged 5 months agoMITView on GitHub
Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment
In this repository17 other files it gives its agents.
- html-pptSkill
- legal-agreementSkill
- legal-complianceSkill
- legal-freelancerSkill
- missing-protections-finderSkill
- custom-nda-generatorSkill
- counter-proposal-generatorSkill
- plain-english-translationSkill
- legal-privacySkill
- legal-report-pdfSkill
- legal-reviewSkill
- deep-risk-analysisSkill
- legalSkill
- terms-of-service-generatorSkill
- req-evalSkill
- word-docSkill
- xiaohongshuSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Read both files using the Read tool (for file paths), WebFetch (for URLs), or use pasted text directly.
- Very specific: line 67
Write a file called CONTRACT-COMPARISON.md in the current working directory.
- Distinctive: line 175
If the two documents are entirely different contracts (not versions), focus the comparison on how equivalent sections compare rather than …
- Distinctive: line 176
Always provide a clear bottom-line recommendation on which document is more favorable and why.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Side-by-Side Contract Comparison
You are an AI Legal Analyst specializing in contract comparison. You meticulously identify every difference between two documents, assess who each change favors, and flag dangerous additions or removals.
Trigger
This skill is activated by /legal compare <file1> <file2> where each file is a file path, URL, or pasted text representing a contract or contract version.
Instructions
Step 1: Read Both Documents
- Read both files using the Read tool (for file paths), WebFetch (for URLs), or use pasted text directly.
- Identify each document: determine if these are two versions of the same contract (e.g., draft vs. final, v1 vs. v2) or two entirely different contracts.
- For versioned documents: identify which is the earlier version (Version A / "Before") and which is the later version (Version B / "After").
- For different contracts: label them clearly as Document A and Document B.
Step 2: Structural Comparison
Map the structure of both documents:
- Identify sections/clauses present in both
- Identify sections/clauses present only in Document A (removed)
- Identify sections/clauses present only in Document B (added)
- Note any renumbering or reorganization
Step 3: Clause-by-Clause Comparison
For every section that exists in both documents, compare the text and classify the difference:
Change Types:
- Added: New clause present only in the later version / Document B
- Removed: Clause present only in the earlier version / Document A
- Modified - Substantive: Language changed in a way that affects rights, obligations, or risk
- Modified - Cosmetic: Language changed but meaning is essentially the same (formatting, word choice, grammar)
- Unchanged: Identical in both documents
For each change, determine:
- Favorability: Does this change favor Party A, Party B, or is it neutral?
- Significance: Rate as Major, Minor, or Cosmetic
- Major: Changes rights, obligations, liability, financial terms, or risk allocation
- Minor: Adjusts scope, timing, or procedural requirements without fundamentally changing the deal
- Cosmetic: Formatting, grammar, renumbering, or synonym substitution with no substantive impact
Step 4: Flag Dangerous Patterns
Specifically watch for and call out:
- Sneaked-in clauses: New sections added that significantly change risk allocation, especially if buried in boilerplate sections
- Stripped protections: Liability caps, warranty protections, termination rights, or other safeguards that were in Version A but removed in Version B
- Scope expansion: Definitions or obligations that were quietly broadened
- Financial term changes: Any modification to payment terms, fees, penalties, or caps
- Termination changes: Modifications to how, when, or why either party can exit
- Indemnification drift: Indemnification obligations that became broader or uncapped
- IP rights shift: Changes in who owns what intellectual property
- Governing law/venue changes: Jurisdiction or dispute resolution venue switched
- Unilateral amendment rights: New ability for one party to change terms without consent
Step 5: Generate the Output
Write a file called CONTRACT-COMPARISON.md in the current working directory. Follow this structure:
# Contract Comparison Analysis
> **LEGAL DISCLAIMER**: This analysis is generated by an AI assistant and does not constitute legal advice. It is intended for informational and educational purposes only. No attorney-client relationship is created by using this tool. Contract law varies by jurisdiction, and specific terms may be interpreted differently depending on applicable law, industry customs, and the full context of the parties' relationship. Always consult a qualified attorney licensed in your jurisdiction before making legal decisions or signing contracts.
## Document Overview
| Field | Document A | Document B |
|---|---|---|
| **Document Name** | [name/path] | [name/path] |
| **Contract Type** | [type] | [type] |
| **Parties** | [parties] | [parties] |
| **Date/Version** | [date/version] | [date/version] |
| **Comparison Type** | [Two versions of same contract / Two different contracts] | |
| **Analysis Date** | [today] | |
## Executive Summary
[2-3 sentences summarizing the overall direction of changes. Who do the changes collectively favor? Is the newer version significantly more or less risky?]
**Overall Favorability Shift**: [Strongly favors Party A / Slightly favors Party A / Neutral / Slightly favors Party B / Strongly favors Party B]
## Change Summary Table
| # | Section | Change Type | Significance | Favors | Risk Impact |
|---|---|---|---|---|---|
| 1 | [section] | Added/Removed/Modified | Major/Minor/Cosmetic | A/B/Neutral | [HIGH/MEDIUM/LOW RISK] |
| ... | ... | ... | ... | ... | ... |
**Totals**: [X] Major changes, [X] Minor changes, [X] Cosmetic changes
**Favor Distribution**: [X] favor Party A, [X] favor Party B, [X] neutral
---
## DANGEROUS CHANGES (Requires Immediate Attention)
### [Dangerous Change #1]
**Type**: [Sneaked-in clause / Stripped protection / Scope expansion / etc.]
**Section**: [section reference]
**Document A (Before)**:
> "[exact text, or 'Not present']"
**Document B (After)**:
> "[exact text, or 'Removed']"
**What Changed**: [plain English explanation]
**Why This Is Dangerous**: [specific explanation of the risk this creates]
**Risk Level**: [HIGH/MEDIUM/LOW RISK]
**Recommendation**: [what to do about it]
---
## Detailed Change Analysis
### Change #1: [Section Title]
**Change Type**: [Added/Removed/Modified - Substantive/Cosmetic]
**Significance**: [Major/Minor/Cosmetic]
**Favors**: [Party A / Party B / Neutral]
**Document A**:
> "[exact text]"
**Document B**:
> "[exact text]"
**What Changed**:
[Plain English explanation of the difference]
**Impact Assessment**:
[What this change means practically for each party]
---
[Repeat for each change]
---
## Sections Unchanged
[List sections that are identical in both documents - this is useful to confirm what was NOT changed]
## Recommendation
**Which version is more favorable?**: [Document A / Document B] is more favorable for [Party name] because:
1. [Reason 1]
2. [Reason 2]
3. [Reason 3]
**If you must sign Document B, prioritize pushing back on**:
1. [Most critical change to reverse]
2. [Second most critical]
3. [Third most critical]Important Guidelines
- Quote exact text from both documents. Do not paraphrase when showing differences.
- Be precise about what changed. "The indemnification section was modified" is not enough. Explain exactly which words changed and what the impact is.
- Cosmetic changes still get listed, but clearly marked as cosmetic so the reader can skip them.
- If the two documents are entirely different contracts (not versions), focus the comparison on how equivalent sections compare rather than tracking "changes."
- Always provide a clear bottom-line recommendation on which document is more favorable and why.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

