MCPInstall

counter-proposal-generator

Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

Installs
67
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

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

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads counter-proposal-generator automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

```text
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.

FAQ

What does the counter-proposal-generator skill do?

Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

How do I install counter-proposal-generator?

Run npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill counter-proposal-generator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/counter-proposal-generator/ (personal) or .claude/skills/counter-proposal-generator/ (project).

Which AI agents can use counter-proposal-generator?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is counter-proposal-generator safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains counter-proposal-generator?

It is published by zubair-trabzada in zubair-trabzada/ai-legal-claude. It has 67 recorded installs.

More from zubair-trabzada/ai-legal-claude

View all →

terms-of-service-generator

zubair-trabzada/ai-legal-claude

Open the skill to read its SKILL.md instructions.

deep-risk-analysis

zubair-trabzada/ai-legal-claude

Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance

contract-comparison

zubair-trabzada/ai-legal-claude

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

missing-protections-finder

zubair-trabzada/ai-legal-claude

Identifies critical clauses and protections that should be in a contract but are missing, with urgency ratings and ready-to-insert language

custom-nda-generator

zubair-trabzada/ai-legal-claude

Open the skill to read its SKILL.md instructions.

plain-english-translation

zubair-trabzada/ai-legal-claude

Open the skill to read its SKILL.md instructions.

Docs & Writing65 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。