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".
What this skill does
# 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 resources
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.