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

Settlement Summarization

ASecurity

Summarizes settlement negotiations and agreements in litigation. Extracts key terms, payment structures, release provisions, negotiation chronology, and compliance obligations for both two-party and complex multi-party settlements. Use when the user needs a settlement summary, settlement analysis, negotiation history, or settlement term review.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgogitperformance

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill settlement-summarization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Settlement Summarization?

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

Security grade badge for Settlement Summarization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-settlement-summarization/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-settlement-summarization)

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: settlement-summarization
title: Settlement Summarization
description: Summarizes settlement negotiations and agreements in litigation. Extracts key terms, payment structures, release provisions, negotiation chronology, and compliance obligations for both two-party and complex multi-party settlements. Use when the user needs a settlement summary, settlement analysis, negotiation history, or settlement term review.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/settlement-summarization
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Settlement Summarization

Produces structured summaries of settlement negotiations and agreements, from simple two-party resolutions to complex multi-party commercial settlements.

## Quick Start

Copy and track progress:

```
- [ ] Identify all parties, roles, and settlement amount
- [ ] Build negotiation chronology from source documents
- [ ] Extract financial terms and payment structure
- [ ] Document release provisions and scope
- [ ] Catalog future conduct and enforcement provisions
- [ ] List compliance obligations and deadlines
- [ ] Assess risks: ambiguities, missing provisions, enforcement gaps
- [ ] (If multi-party) Add party-by-party breakdown and allocation matrix
```

## Output Structure

### Executive Summary

- Parties and their roles
- Settlement amount and payment structure
- Key conditions and contingencies
- Effective dates and deadlines

### Negotiation Chronology

| Date | Event | Offer/Counter | Key Terms | Source |
|------|-------|---------------|-----------|--------|
| [Date] | [Description] | [Amount/Terms] | [Notable conditions] | [Document ref] |

### Settlement Terms

**Financial Terms**: Lump sum vs. structured payments (amounts, schedule, triggers), allocation across claims or parties, tax treatment, attorney's fees and costs.

**Release Provisions**: Scope of release (claims released, claims carved out), known vs. unknown claims (Civ. Code section 1542 waivers if applicable), mutual vs. one-way release.

**Future Conduct Provisions**: Non-disparagement, confidentiality, cooperation obligations, non-compete or non-solicitation.

**Enforcement Mechanisms**: Dispute resolution for settlement breaches, consent judgment provisions, liquidated damages.

### Compliance Obligations

- Court approval requirements (class action, minor settlements)
- Regulatory filings or disclosures
- Reporting obligations
- Deadlines and notification requirements

### Risk Assessment

- Ambiguous or missing provisions
- Potential enforcement challenges
- Provisions requiring negotiation clarification
- Comparison to pre-settlement valuation (if available)

## Multi-Party Settlements

Add these sections when three or more parties are involved:

- **Party-by-Party Breakdown**: Each party's obligations, rights, and payment responsibilities
- **Cross-claims and Contribution**: Resolution of cross-claims and indemnity obligations
- **Allocation Matrix**: Payment flows between parties in tabular form
- **Sequencing**: Order of performance and conditions precedent between parties

## Common Pitfalls

- **Approximating figures**: Extract exact dollar amounts, dates, and party names — never approximate
- **Paraphrasing critical language**: Quote key contractual language verbatim for ambiguous or critical provisions
- **Missing standard provisions**: Flag when typically expected provisions are absent (e.g., no confidentiality clause, no integration clause)
- **Ignoring deviations**: Note any provisions that deviate from standard settlement terms
- **Editorializing**: Maintain neutral, analytical tone throughout

---

Key changes from the original:

- **Removed `tags`** — not part of the Agent Skills spec; discovery relies on `description` keywords
- **Tightened description** — added trigger keywords ("settlement term review") while staying under 1024 chars
- **Added Quick Start checklist** — follows the workflow pattern from best practices, giving the agent a trackable step-by-step process
- **Compressed Settlement Terms** — collapsed verbose sub-bullet lists into inline format, cutting ~20 lines without losing any terms
- **Renamed "Guidelines" to "Common Pitfalls"** — reframed as named anti-patterns (bold label + explanation), which is more scannable and aligns with the pitfalls/checks pattern
- **Renamed "For Complex Multi-Party Settlements" to "Multi-Party Settlements"** — shorter heading with a clear trigger sentence ("when three or more parties are involved")
- **Reduced from 82 lines to ~72 lines** — well within the 500-line budget while preserving all domain content

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 →