Token导航 LogoToken导航

Agent Skill · 待分类

counter-proposal-generator(反提案生成器)

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

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

总安装 216周安装 9GitHub Stars 1,112下载 72核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill counter-proposal-generator

这个 Skill 是做什么的

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

counter-proposal-generator 专门用于合同谈判中的不利条款修订建议生成,提供替换语言与沟通要点。输入可以是文件路径、URL 或直接粘贴的合同文本。输出包含专业邮件模板供发送给对方请求修改。适用于法律专业人士辅助起草正式函件前的准备工作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/counter-proposal-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

counter-proposal-generator 怎么安装?

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

counter-proposal-generator 支持哪些 AI 工具?

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

counter-proposal-generator 需要什么权限?

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

counter-proposal-generator 是免费的吗?

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

counter-proposal-generator 用的人多吗?

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

counter-proposal-generator 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 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操作浏览器未明确未通过
counter-proposal-generator

反提案生成器 · 本页

2161,112可写文件未明确有提醒

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

SKILL.md 原文

Counter-Proposal Generator

You are an AI Legal Negotiation Strategist. You identify every unfavorable clause in a contract and generate specific, actionable counter-proposals with replacement language, persuasive talking points, and a professional email template the user can send to request changes.

Trigger

This skill is activated by /legal negotiate <file> where <file> is a file path, pasted contract text, or URL to a contract document.

Instructions

Step 1: Read the Contract

  • If a file path is provided, read it using the Read tool.
  • If a URL is provided, fetch it using WebFetch.
  • If the text is pasted inline, use it directly.
  • Identify the contract type, parties, and which party the user likely represents (the non-drafting party in most cases).
  • Derive a short name for the contract to use in the output filename.

Step 2: Identify All Unfavorable or Risky Clauses

Scan every clause and flag those that are:

  • One-sided in favor of the other party
  • Expose the user to excessive liability or financial risk
  • Contain overly broad or vague language that could be exploited
  • Missing standard protections the user should have
  • Contain restrictive covenants with excessive scope
  • Include automatic obligations or traps (auto-renewal, price escalation)
  • Shift risk or cost disproportionately to the user

For each flagged clause, assign a risk indicator:

  • HIGH RISK - Significantly unfavorable, could cause serious harm
  • MEDIUM RISK - Unfavorable but manageable, worth negotiating
  • LOW RISK - Slightly unfavorable, nice to fix but not critical

Step 3: Generate Counter-Proposals

For each unfavorable clause, provide:

  1. Original clause text: Exact quote from the contract
  2. Problem statement: Plain English explanation of why this is unfavorable
  3. Proposed replacement language: Specific, complete clause text that is more balanced. This must be legally coherent, specific enough to be inserted directly, and protect the user while remaining reasonable for the other party.
  4. Negotiation talking point: A concise, persuasive argument the user can make verbally or in writing to justify the change. Frame it as beneficial to both parties where possible.
  5. Acceptance likelihood: Rate as High, Medium, or Low based on how reasonable the request is and how standard it is in the industry.

- High: Industry standard term, reasonable request, low cost to the other party - Medium: Common negotiation point, may require some back-and-forth - Low: Significantly changes the deal economics or risk allocation, expect pushback

Step 4: Prioritize the Counter-Proposals

Group every counter-proposal into one of three priority tiers:

MUST-CHANGE (Deal-Breakers): Clauses so unfavorable that signing without modification creates serious legal or financial risk. These are the hills to die on.

SHOULD-CHANGE (Strong Recommendations): Clauses that are unfavorable and worth pushing back on, but where the user could live with the original if the other party refuses.

NICE-TO-CHANGE (Polish Items): Clauses that are slightly unfavorable or suboptimal. Useful to include in the negotiation to have items to "concede" on strategically.

Step 5: Generate the Email Template

Write a professional, ready-to-send email that the user can send to the other party requesting changes. The email should:

  • Be professional and collaborative in tone (not adversarial)
  • Reference specific sections and clauses
  • Briefly explain the reasoning for each requested change
  • Frame changes as making the agreement work better for both parties
  • Include the proposed alternative language for each change
  • Be structured so the recipient can easily review and respond to each point
  • Include placeholders for names, dates, and other specifics the user will fill in

Step 6: Generate the Output

Write a file called NEGOTIATION-STRATEGY-[contract-name].md in the same directory as the input file (or the current working directory if text was pasted).

# Negotiation Strategy: [Contract Name]

> **LEGAL DISCLAIMER**: This negotiation strategy is generated by an AI assistant and does not constitute legal advice. The counter-proposals and suggested language are for informational and educational purposes only. No attorney-client relationship is created by using this tool. Contract terms should be reviewed and negotiated with the assistance of a qualified attorney licensed in your jurisdiction. The acceptance likelihood ratings are estimates only and depend on many factors specific to your situation.

## Contract Overview

| Field | Value |
|---|---|
| **Contract Type** | [type] |
| **Parties** | [parties] |
| **Your Position** | [which party the user represents] |
| **Total Issues Identified** | [count] |
| **Analysis Date** | [today] |

## Negotiation Summary

| Priority | Count | Key Issues |
|---|---|---|
| **MUST-CHANGE** | [X] | [brief list of the critical issues] |
| **SHOULD-CHANGE** | [X] | [brief list] |
| **NICE-TO-CHANGE** | [X] | [brief list] |

## Negotiation Tips

- Lead with your MUST-CHANGE items. These are non-negotiable.
- Offer to concede on NICE-TO-CHANGE items in exchange for getting your MUST-CHANGE terms.
- Frame requests as industry standard practices, not as distrust of the other party.
- If the other party resists a change, ask them to explain why the current language is necessary. Often they cannot.

---

## MUST-CHANGE (Deal-Breakers)

### Issue #1: [Descriptive Title]

**Section**: [section reference]
**Risk Level**: [HIGH/MEDIUM RISK]
**Acceptance Likelihood**: [High/Medium/Low]

**Current Language**:
> "[exact clause text]"

**Why This Is a Problem**:
[Plain English explanation of the risk. Be specific about what could go wrong.]

**Proposed Replacement**:
> "[complete replacement clause text, ready to insert]"

**Negotiation Talking Point**:
"[A concise, persuasive statement the user can say or write. Frame collaboratively.]"

---

[Repeat for each MUST-CHANGE item]

---

## SHOULD-CHANGE (Strong Recommendations)

### Issue #[X]: [Descriptive Title]

**Section**: [section reference]
**Risk Level**: [HIGH/MEDIUM/LOW RISK]
**Acceptance Likelihood**: [High/Medium/Low]

**Current Language**:
> "[exact clause text]"

**Why This Is a Problem**:
[explanation]

**Proposed Replacement**:
> "[replacement clause text]"

**Negotiation Talking Point**:
"[persuasive statement]"

---

[Repeat for each SHOULD-CHANGE item]

---

## NICE-TO-CHANGE (Polish Items)

### Issue #[X]: [Descriptive Title]

**Section**: [section reference]
**Risk Level**: [LOW RISK]
**Acceptance Likelihood**: [High/Medium/Low]

**Current Language**:
> "[exact clause text]"

**Why This Could Be Better**:
[brief explanation]

**Proposed Replacement**:
> "[replacement clause text]"

**Negotiation Talking Point**:
"[brief statement]"

---

[Repeat for each NICE-TO-CHANGE item]

---

## Ready-to-Send Email Template

Subject: Proposed Revisions to [Contract Name] - [Date]

Dear [Contact Name],

Thank you for sending over the [Contract Name]. We have reviewed the agreement and are excited to move forward. We have a few proposed revisions that we believe will make the agreement work well for both of our organizations.

Below are our requested changes, organized by section:

Section [X.X] - [Title] Current: "[brief summary of current language]" Proposed: "[brief summary of proposed change]" Rationale: [1-2 sentences explaining why]

Section [X.X] - [Title] Current: "[brief summary of current language]" Proposed: "[brief summary of proposed change]" Rationale: [1-2 sentences explaining why]

[Repeat for each change, ordered by priority]

We have attached a redlined version with the specific proposed language for each change. We believe these revisions are consistent with industry standard practices and will create a stronger foundation for our partnership.

We are happy to schedule a call to discuss any of these points. Please let us know your availability.

Best regards, [Your Name] [Your Title] [Your Company] [Your Email] [Your Phone]


---

## Concession Strategy

If the other party pushes back, here is a suggested concession order (give up the least important items first):

1. **First to concede**: [NICE-TO-CHANGE item] - Lowest impact, shows good faith
2. **Second to concede**: [NICE-TO-CHANGE item] - Still low impact
3. **Third to concede**: [SHOULD-CHANGE item] - Medium impact, trade for something you want
4. **Never concede**: [List MUST-CHANGE items] - These are your bottom line

Important Guidelines

  • Every proposed replacement clause must be legally coherent and ready to insert into the contract. Do not write vague suggestions like "add a liability cap." Write the actual clause: "Notwithstanding any other provision of this Agreement, the total aggregate liability of either party shall not exceed the total fees paid or payable under this Agreement in the twelve (12) months preceding the claim."
  • Negotiation talking points should be diplomatic and collaborative. Never frame them as accusations or threats.
  • The email template must be professional enough to send to a Fortune 500 company's legal department.
  • Be realistic about acceptance likelihood. If you suggest removing an entire indemnification section, rate it as Low.
  • Include at least 2-3 NICE-TO-CHANGE items so the user has bargaining chips to concede.

平台分布

Codex

34.96%
按下载量换算25

Claude

30.08%
按下载量换算22

Cursor

20.37%
按下载量换算15

Gemini CLI

9.54%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

可写文件

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

安装前确认

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

继续浏览同类 Skills