negotiate
Analyzes contracts for unfavorable or risky clauses and generates prioritized counter-proposals with replacement language. Use when reviewing a contract before signing, preparing for a negotiation, or responding to unfavorable terms. Trigger with "/negotiate" or "generate counter-proposals for this contract".
Best use case
negotiate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyzes contracts for unfavorable or risky clauses and generates prioritized counter-proposals with replacement language. Use when reviewing a contract before signing, preparing for a negotiation, or responding to unfavorable terms. Trigger with "/negotiate" or "generate counter-proposals for this contract".
Teams using negotiate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/negotiate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How negotiate Compares
| Feature / Agent | negotiate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyzes contracts for unfavorable or risky clauses and generates prioritized counter-proposals with replacement language. Use when reviewing a contract before signing, preparing for a negotiation, or responding to unfavorable terms. Trigger with "/negotiate" or "generate counter-proposals for this contract".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Contract Negotiation Strategy Generator
## Overview
Reads a contract or agreement, identifies clauses that are unfavorable, one-sided,
or carry hidden risk, and produces a structured negotiation strategy document with
specific counter-proposals ranked by priority. Benchmarks replacement language
against CommonPaper standard clauses (CC BY 4.0) to ensure proposed alternatives
reflect market norms.
This skill performs analysis only — it does not create new contracts. It reads the
source document and outputs a negotiation strategy in Markdown.
> **Legal Disclaimer:** This skill generates AI-assisted analysis for informational
> purposes only. It does not constitute legal advice. All counter-proposals and
> replacement language must be reviewed by a licensed attorney before use in any
> binding agreement. No attorney-client relationship is created by using this tool.
## Prerequisites
- A contract or agreement file accessible in the workspace (`.md`, `.txt`, or `.pdf`)
- Knowledge of the user's negotiating position (buyer, seller, service provider, etc.)
- Understanding of which party the user represents
## Instructions
1. **Identify the contract.** Locate the contract file using Glob. If multiple contracts
exist, ask the user to confirm which one to analyze.
2. **Read the full contract.** Use Read to ingest the entire document. Note the parties,
effective date, governing law, and contract type.
3. **Classify the user's position.** Determine which party the user represents and their
leverage context (e.g., small vendor vs. enterprise buyer).
4. **Scan for unfavorable clauses.** Evaluate every section against these risk categories:
- **Liability & Indemnification** — unlimited liability, one-sided indemnity, no caps
- **Termination** — termination for convenience without notice, auto-renewal traps
- **IP & Ownership** — broad IP assignment, work-for-hire overreach
- **Payment** — late payment penalties without reciprocal terms, NET-90+
- **Confidentiality** — perpetual obligations, overly broad definitions
- **Non-Compete / Non-Solicit** — excessive scope, duration, or geography
- **Limitation of Liability** — exclusion of consequential damages only for one party
- **Governing Law & Dispute** — inconvenient jurisdiction, mandatory arbitration
- **Data & Privacy** — broad data usage rights, no breach notification
- **Force Majeure** — missing or one-sided
5. **Prioritize findings into three tiers:**
- **MUST-CHANGE** — Clauses that create unacceptable legal or financial risk. Deal-breakers
if not modified.
- **SHOULD-CHANGE** — Clauses that are unfavorable but negotiable. Significant improvement
if changed.
- **NICE-TO-CHANGE** — Minor improvements that strengthen position but are not critical.
6. **Generate counter-proposals.** For each flagged clause:
- Quote the original clause text verbatim
- Explain the specific risk in plain English
- Provide replacement language (benchmark against CommonPaper standard clauses)
- Include a confidence indicator: HIGH (standard market practice), MEDIUM (reasonable
but may face pushback), LOW (aggressive position)
- Write 2-3 negotiation talking points explaining *why* the change is fair
7. **Draft a professional email template.** Create a ready-to-send email that:
- Opens with appreciation for the partnership/opportunity
- Frames changes as "clarifications" or "alignment with market standards"
- References specific clause numbers
- Maintains a collaborative, non-adversarial tone
- Closes with a request for a call to discuss
8. **Compile the strategy document.** Assemble all findings into the output format below.
## Output
Generate a single Markdown file named `NEGOTIATION-STRATEGY-{contract-name}.md` with:
```
# Negotiation Strategy: {Contract Name}
## Summary
- Contract: {name}
- Parties: {Party A} / {Party B}
- Representing: {which party}
- Date analyzed: {date}
- Clauses flagged: {count} ({MUST}: N, {SHOULD}: N, {NICE}: N)
## Risk Overview
{2-3 sentence executive summary of overall contract fairness}
## MUST-CHANGE Clauses
### 1. {Section Reference} — {Short Description}
**Original:** > {quoted text}
**Risk:** {plain English explanation}
**Counter-Proposal:** {replacement language}
**Confidence:** {HIGH/MEDIUM/LOW}
**Talking Points:**
- {point 1}
- {point 2}
## SHOULD-CHANGE Clauses
{same format}
## NICE-TO-CHANGE Clauses
{same format}
## Negotiation Email Draft
{professional email template}
## Benchmarks Referenced
- CommonPaper Standard Cloud Agreement (CC BY 4.0)
- {other relevant standards}
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| No contract file found | Missing or wrong path | Ask user for the file location |
| Ambiguous party role | Cannot determine who user represents | Ask user to clarify their position |
| Non-English contract | Skill optimized for English common law | Warn user; provide best-effort analysis with caveats |
| Highly specialized terms | Domain-specific clauses (e.g., pharma, defense) | Flag as requiring specialist review |
| PDF format unreadable | Scanned image PDF | Ask user for text version or OCR output |
## Examples
**Example 1: SaaS Vendor Agreement**
Request: "Analyze this vendor agreement and generate counter-proposals — we're the customer"
Result: Strategy document identifying 12 clauses across 3 tiers:
- MUST-CHANGE: Unlimited liability for customer (cap at 12 months fees), auto-renewal
without 60-day notice window
- SHOULD-CHANGE: NET-60 payment terms (propose NET-30 with 2% early payment discount),
broad IP license grant
- NICE-TO-CHANGE: Governing law in vendor's state (propose mutual arbitration)
**Example 2: Freelancer Service Agreement**
Request: "Review this freelance contract — I'm the freelancer"
Result: Strategy identifying one-sided IP assignment (propose limited license), missing
kill fee provision (propose 25% kill fee after kickoff), and 2-year non-compete
(propose narrowing to direct competitors for 6 months).
## Resources
- [CommonPaper Standard Agreements](https://commonpaper.com/standards/) — CC BY 4.0 open-source contract standards
- [Bonterms Cloud Terms](https://bonterms.com/) — CC BY 4.0 standardized cloud contracting
- [American Bar Association Model Agreements](https://www.americanbar.org/) — professional benchmarks
- [SCORE Contract Negotiation Guide](https://www.score.org/) — SBA-funded small business resourcesRelated Skills
schema-optimization-orchestrator
Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"
test-skill
Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.
example-skill
Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".
testing-visual-regression
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
generating-unit-tests
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
generating-test-reports
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
orchestrating-test-execution
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
managing-test-environments
Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".
generating-test-doubles
Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures. Trigger with phrases like "generate mocks", "create test doubles", or "setup stubs".
generating-test-data
Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".
analyzing-test-coverage
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
managing-snapshot-tests
Create and validate component snapshots for UI regression testing. Use when performing specialized testing. Trigger with phrases like "update snapshots", "test UI snapshots", or "validate component snapshots".