jeremylongshore/tons-of-skills-marketplace / plugins/business-tools/general-legal-assistant/skills/contract-compare
contract-compare
VerifiedCompare two contract versions with clause-level evidence, coverage limits and qualified analysis of possible effects for the identified parties. Use when reviewing a revised contract or redline. Trigger with "contract-compare" or "compare these two contracts".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.4 KB |
| references/report-and-review.md | markdown | 4.2 KB |
references/report-and-review.md
View on GitHub# Comparison report and evidence review
## Document and coverage record
Record the selected matter label, report date, baseline and revision identifiers,
source paths and which party's perspective is being considered. Reuse supplied
version labels; do not invent file hashes or signatures. Record hashes only when
actually computed with an available authorized tool.
List the pages/sections/exhibits read and each known gap. Note whether the visible
text is clean, tracked-change markup, a rendered PDF or an extraction. OCR errors,
missing tables, hidden annotations, signatures and unavailable incorporated terms
can limit the result. Normalization must not drop amounts, negations or defined
term capitalization that may affect the comparison.
## Clause map
| Baseline locator | Revision locator | Alignment status | Evidence or limit |
| ------------------- | --------------------------------- | ----------------------------------------- | -------------------------------------------------- |
| Actual section/page | Actual corresponding section/page | Aligned, moved, new, absent or unresolved | Text used for mapping, or why mapping is uncertain |
Use absent/removal only within established coverage. Do not double-count a moved
clause as one deletion plus one addition. A relocated clause can also have a
wording change; show both aspects without inflating the finding count.
## Finding record
For each finding, include:
- **ID and type:** stable identifier plus added/removed/modified/moved.
- **Locations:** original and revised section/page, with exact version labels.
- **Evidence:** minimal exact excerpts; clearly identify omitted material and keep
quotation boundaries honest. Preserve the documents unchanged.
- **Observation:** the actual textual change, separate from interpretation.
- **Dependencies:** defined terms, cross-references, caps, exceptions, schedules or
precedence provisions inspected, and any unavailable dependency.
- **Possible effect:** who may benefit or incur an obligation under stated
assumptions; use neutral, unclear or context-dependent when appropriate.
- **Priority and next question:** tied to the user's stated objective; identify the
context or legal review needed before deciding what to negotiate.
The report may group presentation-only edits, but must not hide a material wording
change inside that group. Do not infer intentional concealment from a small edit,
renumbering or an expanded definition.
## Counts and conclusions
If reporting counts, reconcile them with finding IDs and explain how moves and
multiple changes in one clause were counted. Do not turn counts or subjective
severity weights into legal safety, likely damages or negotiation success.
One material change can outweigh many cosmetic edits.
A term's absence from one document is a textual observation. Any assertion about
rights, enforceability or default rules requires applicable current law and full
contract context. Do not present a generic UCC, common-law or template reference
as a rule governing every supplied contract. Frame unsupported legal questions for
qualified review instead of inventing citations or conclusions.
## Final review
Check baseline direction and party mapping, both locators and each quotation,
coverage gaps, material dependencies, counts and priority rationale. Verify the
selected output path and preserve unrelated reports. A report draft is not a
contract amendment, legal opinion or authorization to send messages or accept terms.
## Primary workflow guidance
Reviewed 2026-10-25. These sources address professional use of AI and output review;
they do not determine the interpretation of the user's contract or create a
universal jurisdictional rule.
- [Florida Bar Opinion 24-1](https://www.floridabar.org/etopinions/opinion-24-1/):
advisory guidance emphasizes confidentiality, independent professional judgment
and verification of AI-assisted work.
- [ABA announcement of Formal Opinion 512](https://www.americanbar.org/news/abanews/aba-news-archives/2024/07/aba-issues-first-ethics-guidance-ai-tools/):
discusses competence, confidentiality and review responsibilities when lawyers
use generative AI.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |