Agent skill · AI & Agents

settlement-pressure-tester-larissa-meredith-flister

This skill stress-tests a proposed settlement position before an offer goes out or comes back: the assumptions it depends on, your leverage and the opponent’s, the evidential weaknesses, the likely opponent response, and the timing and costs pressures around it. It structures settlement judgment for a better-informed decision; it does not advise whether to settle.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill settlement-pressure-tester-larissa-meredith-flister --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 11 KB
Bundled scripts: none
Version: 2026-06-11
Declared author: Larissa Meredith-Flister
Path: skills/settlement-pressure-tester-larissa-meredith-flister/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Settlement Pressure Tester ## Purpose Settlement positions often sound commercial, but they still rest on assumptions about proof, leverage, timing, and risk. A number that feels reasonable can be built on a liability theory the evidence will not carry, or a confidence about the opponent's appetite that has never been tested. This skill stress-tests a proposed settlement position so the team can see what it actually depends on before an offer goes out or comes back. You are acting as an experienced litigation solicitor advising internally. Your job is to find the pressure points, not to cheerlead. Core discipline: - Do not simply summarise the position back. - Do not assume the user's case is as strong as presented. - Do not assume settlement is either desirable or undesirable. - Do not invent facts, evidence, procedural steps, quantum, costs, dates, or opponent motivations. - Where something is speculative, label it speculative. - Where information is missing, say what is missing before giving firm conclusions. Be candid about weakness. A pressure test that flatters the position is useless — its whole value is telling the team what they would rather not hear before the opponent

What's inside
Steps it walks through
  1. Purpose
  2. When the user has not given you enough
  3. Output structure
  4. 1. Settlement position in one paragraph
  5. 2. Case strength assessment
  6. 3. What the settlement position assumes
  7. 4. Leverage points
  8. 5. Opponent's likely leverage
  9. 6. Litigation risk
  10. 7. BATNA / WATNA analysis
  11. 8. Too aggressive, too conservative, or broadly defensible?
  12. 9. Likely opponent response
  13. 10. Timing and procedural pressure
  14. 11. Costs and proportionality
Ships with 2 files
  • README.md
  • evals/evals.json
More from awesome-legal-skills
All skills →
About this skill
What does the settlement-pressure-tester-larissa-meredith-flister skill do?

This skill stress-tests a proposed settlement position before an offer goes out or comes back: the assumptions it depends on, your leverage and the opponent’s, the evidential weaknesses, the likely opponent response, and the timing and costs pressures around it. It structures settlement judgment for a better-informed decision; it does not advise whether to settle.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill settlement-pressure-tester-larissa-meredith-flister --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going