Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Negotiation Support

ASecurity

Generates a strategic negotiation support document with leverage analysis, BATNA assessment, risk matrix, and issue-by-issue tactical planning. Use when preparing for settlement conferences, mediations, contract negotiations, deal structuring, or dispute resolution strategy sessions.

15 stars
0 votes
0 copies
1 views
Added 6/7/2026
ai-agentsgogitdocumentation

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill negotiation-support --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Negotiation Support?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Negotiation Support
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-negotiation-support/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-negotiation-support)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: negotiation-support
title: Negotiation Support
description: Generates a strategic negotiation support document with leverage analysis, BATNA assessment, risk matrix, and issue-by-issue tactical planning. Use when preparing for settlement conferences, mediations, contract negotiations, deal structuring, or dispute resolution strategy sessions.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/negotiation-support
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
tags: [analysis, memo, transactional]
---

# Negotiation Support

Strategic negotiation roadmap synthesizing case materials into leverage analysis, risk assessment, and tactical recommendations.

## Prerequisites

1. **Matter context** — parties, relationship history, negotiation type (settlement / contract / transactional / dispute resolution)
2. **Documents** — contracts, correspondence, prior agreements, discovery, financials
3. **Client objectives** — goals, constraints, authority limits, timeline
4. **Negotiation history** — prior offers, counteroffers, impasses, tentative agreements

## Quick Start

1. Gather prerequisites above.
2. Produce each output section in order (Executive Summary through Action Items).
3. Cite source documents for every factual claim.
4. Mark unconfirmed legal authority with `[VERIFY]`.
5. Label the document as privileged work product.

## Output Structure

### 1. Executive Summary

| Element | Content |
| --- | --- |
| Negotiation type | Settlement / contract / transactional / dispute resolution |
| Parties | Names, roles, relationship summary |
| Core objectives | Client's 3–5 primary goals, ranked |
| Critical issues | Top issues driving negotiation |
| Recommended strategy | Integrative vs. distributive; approach in 2–3 sentences |
| Key recommendation | Single most important strategic action |

### 2. Factual Background

Chronological narrative with cited sources covering:
- Relationship history and negotiation genesis
- Key dates, amounts, communications, commitments
- Prior negotiation attempts and outcomes
- Current procedural posture or deal status

### 3. Interests & Positions Analysis

| | Client | Opposing Party |
| --- | --- | --- |
| Stated positions | What they demand | What they demand |
| Underlying interests | Economic, operational, reputational, relational | Same categories (estimated) |
| Constraints | Authority, timeline, regulatory | Likely constraints |
| Priorities | Rank order of issues | Estimated rank order |
| Pressure points | Internal deadlines, stakeholder demands | Likely pressures |

### 4. Leverage Assessment

Rate each factor High / Medium / Low for both sides:

| Leverage Type | Client | Opposing Party |
| --- | --- | --- |
| Legal — claims strength, precedent, contractual position | | |
| Economic — resources, market position, alternatives | | |
| Informational — asymmetric knowledge, discovery exposure | | |
| Timing — deadlines, limitations periods, market windows | | |
| Relational — ongoing relationship value, reputation | | |

### 5. BATNA Analysis

| | Client | Opposing Party (est.) |
| --- | --- | --- |
| Best alternative | | |
| Likely outcome if no deal | | |
| Cost of no deal | | |
| Timeline of alternative | | |
| Risks of alternative | | |
| **Reservation point** | Minimum acceptable | Estimated walk-away |
| **Target outcome** | Aspirational realistic goal | |

### 6. Risk Matrix

| Risk | Type | Likelihood | Impact | Mitigation |
| --- | --- | --- | --- | --- |
| | Legal / Business / Strategic | H/M/L | H/M/L | Specific action |

Flag categories: litigation exposure, regulatory concerns, contractual weaknesses, reputational damage, precedent-setting risk, relationship damage.

### 7. Issue-by-Issue Plan

For each significant issue:

| Issue | Opening | Target | Walk-Away | Value to Us | Value to Them |
| --- | --- | --- | --- | --- | --- |
| | | | | H/M/L | H/M/L |

Identify for each issue:
- **Trade opportunities** — low-cost concessions that are high-value to the other side
- **Package proposals** — bundled combinations that create value
- **Sequencing** — optimal order to address issues

### 8. Tactical Recommendations

**Approach:** integrative vs. distributive rationale, anchoring strategy, concession pattern (graduated / reciprocal / contingent), framing.

**Anticipated arguments & responses:**

| Opposing Argument | Response | Supporting Authority / Facts |
| --- | --- | --- |
| | | Cite documents, precedent, statutory provisions |

**Process recommendations:**
- Confidentiality protocol (NDA, FRE 408 / settlement privilege)
- Stakeholder involvement and escalation triggers
- Documentation protocol for offers and tentative agreements
- Expert input needs (financial, technical, industry)

### 9. Action Items

| Action | Owner | Deadline | Priority |
| --- | --- | --- | --- |
| Pre-session preparations | | | |
| Information to gather | | | |
| Stakeholder decisions needed | | | |
| Analysis to complete | | | |

Include negotiation timeline with milestones.

## Guidelines

- **Candid assessment** — acknowledge weaknesses; do not overstate leverage.
- **Cite sources** — tie every factual claim to specific materials reviewed.
- **Jurisdiction-aware** — flag rules affecting negotiation (FRE 408, state settlement privilege, mandatory mediation).
- **Confidentiality** — mark as privileged work product; note attorney-client privilege applicability.
- **Actionable specificity** — tailor every recommendation to the matter facts; no generic advice.
- **Authority verification** — mark unconfirmed authority with `[VERIFY]`.
- **Living document** — revise as new information emerges during negotiation.

## Troubleshooting

- **Missing client authority limits**: Flag gap and request before drafting BATNA reservation points.
- **Sparse opposing-party information**: Mark estimated fields explicitly; recommend discovery or informal information-gathering steps.
- **Multi-party negotiation**: Duplicate the Interests & Leverage tables per party; note coalition dynamics.
- **Cross-jurisdictional matters**: Identify each jurisdiction's settlement privilege rules separately; flag conflicts.

---

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →