Token导航 LogoToken导航

Agent Skill · 待分类

contract-comparison(合同比较)

contract-comparison 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

contract-comparison 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为可写文件;许可证信息还不明确,第三方扫描有未通过项,按安装量在待分类类的 11,209 个 Skill 里排第 9,979。

总安装 218周安装 9GitHub Stars 1,070下载 71核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:contract-comparison(合同比较)
来源仓库:https://github.com/zubair-trabzada/ai-legal-claude
仓库路径:skills/contract-comparison
安装命令:
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contract-comparison
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contract-comparison

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

contract-comparison 用于逐条对比两份合同文本,识别差异并评估对各方的利弊影响。适合在 Codex、Claude、Cursor、Gemini CLI 中审核修订版本、谈判支持或合规检查时使用。可输出带追踪标记的修改建议、风险评级及协商要点,提升审阅效率。

需同时提供两个合同的文件路径、URL 或粘贴文本,确保内容完整可比。注意其仅提供技术分析,不替代法律判断,重要结论须经执业律师确认。

来源仓库内路径:skills/contract-comparison

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contra…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要可写文件,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

contract-comparison 怎么安装?

在终端执行 npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill contract-compari…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

contract-comparison 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

contract-comparison 需要什么权限?

权限级别是可写文件。该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

contract-comparison 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

contract-comparison 用的人多吗?

公开数据是累计安装 218 次,近一周安装 9 次,下载 71 次,GitHub 1,070 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

contract-comparison 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 1,070 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
contract-comparison

合同比较 · 本页

2181,070可写文件未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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.

平台分布

Codex

36.15%
按下载量换算26

Claude

28.04%
按下载量换算20

Cursor

17.27%
按下载量换算12

Gemini CLI

10.08%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

可写文件

该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills