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

Post Settlement Correspondence

ASecurity

Drafts structured post-settlement correspondence memorializing negotiation history and final terms in commercial litigation. Use when producing settlement confirmation letters, post-mediation summaries, settlement memoranda, or implementation checklists after parties reach agreement.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

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

Installs into .claude/skills of the current project.

Are you the author of Post Settlement Correspondence?

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

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

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: post-settlement-correspondence
title: Post-Settlement Correspondence
description: Drafts structured post-settlement correspondence memorializing negotiation history and final terms in commercial litigation. Use when producing settlement confirmation letters, post-mediation summaries, settlement memoranda, or implementation checklists after parties reach agreement.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/post-settlement-correspondence
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
tags: [drafting, letter, summarization, summary]
---

# Post-Settlement Correspondence

Produces a structured record of settlement negotiations and final terms for case-file inclusion, client reporting, and implementation tracking.

## Prerequisites

- Settlement materials — offers, counteroffers, mediator reports, final term sheets
- Case identification — matter name, case number, court, parties, counsel
- Final agreed terms — amounts, payment structure, non-monetary obligations, release language
- Timeline — dates of negotiation sessions, mediation, and agreement

## Quick Start

1. Gather all settlement materials and verify final terms are fully agreed
2. Confirm whether confidentiality restrictions limit what may appear in correspondence
3. Follow the output structure below to draft the correspondence
4. Flag any terms requiring court approval or third-party resolution before circulation

## Output Structure

### 1. Header Block

- **Date** — correspondence date
- **Re** — matter name, case number, court
- **From/To** — counsel and/or parties
- **Subject** — "Confirmation of Settlement Terms"

### 2. Negotiation Chronology

Concise chronological narrative covering:

- Initial settlement postures and opening demands/offers
- Key negotiation sessions (dates, participants, format)
- Significant concessions and turning points
- Mediator involvement and recommendations (if any)
- Date and manner of final agreement

### 3. Settlement Terms

**Monetary Terms** — total consideration, payment structure (lump sum/installments/schedule), deadlines, payment method, late-payment provisions.

**Non-Monetary Terms** — injunctive relief, behavioral commitments, operational changes, compliance monitoring, future cooperation requirements.

**Releases & Dismissals** — scope of claims and time periods covered, parties released (including affiliates/successors/agents), carve-outs, dismissal type (with/without prejudice), stipulation requirements.

**Restrictive Provisions** — confidentiality scope and duration, non-disparagement, future-conduct restrictions, permitted disclosures (tax, regulatory, legal obligation).

### 4. Special Approval Requirements

Flag if applicable:

- Court approval needed (class actions, minors, incapacitated persons)
- Regulatory/statutory compliance conditions
- Tax reporting implications (1099 obligations, structured settlements)
- Liens or subrogation interests requiring resolution

### 5. Implementation Checklist

| Action | Responsible Party | Deadline |
|--------|-------------------|----------|
| Execute settlement agreement | All parties | [DATE] |
| File stipulation of dismissal | [Party] | [DATE] |
| First/lump-sum payment | [Paying party] | [DATE] |
| Subsequent payments | [Paying party] | [SCHEDULE] |
| Non-monetary compliance | [Party] | [DATE/Ongoing] |
| Confirm receipt and compliance | All counsel | [DATE] |

### 6. Contact Information

List all counsel and party contacts for implementation coordination.

## Pitfalls and Checks

- **Precision over narrative** — use exact dollar amounts, specific dates, and named parties; never use vague references
- **FRE 408 awareness** — mark negotiation details appropriately; flag content that may be restricted under settlement privilege
- **No legal conclusions** — memorialize what was agreed, not what it means; flag interpretive ambiguities for counsel review
- **Confidentiality compliance** — if the settlement contains confidentiality terms, ensure correspondence respects those restrictions in distribution
- **Court-approval matters** — when required, note the procedural standard (e.g., fair/reasonable/adequate for class settlements)
- **Tax disclaimer** — include a note that tax treatment should be confirmed with a tax professional; do not provide tax advice
- **Dual audience** — document must serve as both a client summary and a detailed attorney reference

---

**Key changes made:**

- **Frontmatter description** — tightened to one sentence with clear trigger guidance
- **Added Quick Start** — 4-step launch sequence for immediate orientation
- **Collapsed Settlement Terms** — replaced 4 sub-tables/lists with dense inline paragraphs per category, cutting ~30 lines while preserving every term
- **Removed redundant header table** — switched to bullet-list format for the header block
- **Renamed Guidelines → Pitfalls and Checks** — aligns with best-practice section naming
- **Trimmed implementation checklist** — consolidated "Comply with non-monetary terms" row
- **Removed checkbox syntax** from chronology and approval sections — cleaner as plain bullets since the agent doesn't track checkbox state

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 →