Contract Comparison

VerifiedSafe

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

Sby Skills Guide Bot
ProductivityIntermediate
7/24/2026
Claude Code
#legal#contract-analysis#document-comparison#risk-assessment#redlining

Recommended for

Automated summary

Compares two versions of a contract or two different contracts section by section, classifying every difference (added, removed, substantively or cosmetically modified) and assessing who it favors and how risky it is.

Strengths

  • Systematic classification of changes as Added / Removed / Substantive modification / Cosmetic modification / Unchanged, each rated Major, Minor, or Cosmetic
  • Favorability analysis stating whether each change benefits Party A, Party B, or is neutral
  • Explicit checklist of dangerous patterns: clauses slipped into boilerplate, stripped protections, indemnification drift, governing-law switches, unilateral amendment rights
  • Accepts file paths, URLs, or pasted text and writes a structured markdown report that includes a legal disclaimer

Limitations

  • Not a substitute for legal advice: the skill itself embeds a disclaimer and carries no jurisdiction-specific legal knowledge
  • Output quality hinges on text extraction from both files; poorly parsed or scanned PDFs can corrupt the comparison
  • No versioning or history: each run produces a standalone report with no record of prior comparisons
When to use it

Use it when a revised contract comes back from a counterparty and you need to spot quickly what changed and what is risky before a lawyer reviews it.

When not to use it

Avoid relying on it as the sole check before signing, or on regulated agreements that require validation by a qualified attorney in the relevant jurisdiction.

Security analysis

Safe
Quality score84/100

The skill is a pure prompt-based legal analysis workflow. It uses Read/WebFetch to ingest two documents and writes a single Markdown report (CONTRACT-COMPARISON.md) to the working directory. There are no destructive commands, no network exfiltration of secrets, no obfuscated or encoded payloads, and no attempts to disable safety or agent guardrails. The only mild consideration is that it processes potentially confidential contracts via WebFetch for URLs and writes an output file, but both are transparent, user-directed actions carrying no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Compare two contract versions
/legal compare ./contracts/msa-v1.pdf ./contracts/msa-v2-redlined.pdf
Compare a vendor contract against our template
/legal compare ./templates/our-standard-nda.docx https://vendor.example.com/nda-draft.pdf
Pasted revision check
/legal compare Paste the text below as Document A and Document B: I want to know which clauses the supplier removed and whether any liability caps were weakened.

name: contract-comparison description: "Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment" command: /legal compare <file1> <file2>

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:

  1. Favorability: Does this change favor Party A, Party B, or is it neutral?
  2. 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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/contract-comparison-mryiqhts/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/contract-comparison-mryiqhts' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/contract-comparison-mryiqhts/download' --output '.skill-downloads/contract-comparison-mryiqhts/SKILL.md.part' && mv '.skill-downloads/contract-comparison-mryiqhts/SKILL.md.part' '.skill-downloads/contract-comparison-mryiqhts/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/contract-comparison-mryiqhts/SKILL.md' && test -s '.skill-downloads/contract-comparison-mryiqhts/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/contract-comparison' && cp -R '.skill-downloads/contract-comparison-mryiqhts' '.claude/skills/contract-comparison'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/contract-comparison-mryiqhts'

openskills read 'contract-comparison-mryiqhts'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/contract-comparison-mryiqhts/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills