Agent skill

contract-compare

Compares two contract versions side-by-side to detect added, removed, and modified clauses with favorability analysis. Use when a user receives a revised contract or redline and needs to understand what changed and who each change favors. Trigger with "/contract-compare" or "compare these two contracts". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill contract-compare --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Intent Solutions <jeremy@intentsolutions.io>
Allowed tools: ReadGlobGrep
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/contract-compare/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Contract Compare — Version Comparison and Favorability Analysis Side-by-side contract comparison skill that identifies every change between two versions, classifies each change by type and severity, and determines which party each modification favors. Essential during negotiation rounds when a counterparty returns a revised draft. ## Overview When a counterparty returns a revised contract, the changes they made — and the changes they quietly did not make — tell a story about their priorities and strategy. This skill performs a structured comparison that surfaces not just what changed, but the strategic significance of each change. It detects three dangerous patterns that manual review frequently misses: indemnification drift (gradual shifting of liability across revisions), IP scope creep (expanding intellectual property assignment through small wording tweaks), and definition manipulation (redefining key terms to alter clause meaning without touching the clauses themselves). ## Prerequisites - Two versions of the same contract must be provided, either as: - Two file paths (e.g., `contract-v1.pdf` and `contract-v2.pdf`) - One file path and one pasted text block - Two pasted text

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Output
  5. Error Handling
  6. Examples
  7. Resources
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the contract-compare skill do?

Compares two contract versions side-by-side to detect added, removed, and modified clauses with favorability analysis. Use when a user receives a revised contract or redline and needs to understand what changed and who each change favors. Trigger with "/contract-compare" or "compare these two contracts". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill contract-compare --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going