
contract-comparison
Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment
- Installs
- 69
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contract-comparison- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads contract-comparison automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
FAQ
What does the contract-comparison skill do?
Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment
How do I install contract-comparison?
Run npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contract-comparison in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/contract-comparison/ (personal) or .claude/skills/contract-comparison/ (project).
Which AI agents can use contract-comparison?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is contract-comparison safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains contract-comparison?
It is published by zubair-trabzada in zubair-trabzada/ai-legal-claude. It has 69 recorded installs.
More from zubair-trabzada/ai-legal-claude
terms-of-service-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
deep-risk-analysis
zubair-trabzada/ai-legal-claude
Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance
missing-protections-finder
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
counter-proposal-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
custom-nda-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
plain-english-translation
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.