Writes a settlement letter on the right footing — and warns you when marking it 'without prejudice' won't actually keep it out of court. A genuine settlement letter is normally protected (the judge can't see it), but only if the substance is a real attempt to settle, and even then there are exceptions. The skill picks the correct footing — without prejudice (WP), without prejudice save as to costs (WPSATC / Calderbank), or open — drafts the finished letter, and surfaces the Unilever v Procter & Gamble exceptions that get WP material admitted despite the label, which a plain template won't flag. Built for juniors and in-house counsel drafting a settlement or Calderbank offer who need the footing right the first time. Use when the user asks to draft a WP letter, a Calderbank, a settlement letter, or wants to know whether material is likely protected from disclosure.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill without-prejudice-drafter-andrew-bird
| Footing | Disclosure at trial | Use |
|---|---|---|
| Open | Yes — fully admissible | Statements of case, demands, pre-action letters not yet in negotiation |
| Without prejudice (WP) | No — inadmissible to prove liability or quantum | Genuine settlement negotiations |
| Without prejudice save as to costs (WPSATC) / Calderbank | Inadmissible on liability/quantum; intended to be admissible on costs after judgment | Settlement offers where the offeror wants costs protection but cannot use CPR Part 36 (e.g. Employment Tribunal) or wants Calderbank flexibility |
Labelling a letter WPSATC signals the intended footing; it does not by itself secure costs protection. Whether the court reads the letter on costs, and what weight it gives it, is a matter for the court's discretion (CPR 44.2) on the facts. The footing is a proposal, not a guarantee.
Three conditions:
A letter labelled "without prejudice" that does not satisfy these conditions is not protected. A letter that satisfies them but is not labelled is still protected — the label is evidence of intention, but substance prevails (Rush & Tompkins Ltd v Greater London Council [1989] AC 1280).
WP protection is not absolute (Unilever plc v Procter & Gamble Co [2000] 1 WLR 2436, [2000] EWCA Civ 11). The categories below are illustrative, not a closed or settled set — the courts treat them as fact-sensitive, so confirm the current scope before relying on any one of them. The court has admitted WP material in evidence in situations including the following. Do not over-extend these; treat anything outside a squarely-decided category as in need of verification rather than asserting protection is lost:
A letter discussing a settlement that also makes a threat or admits a crime is exposed under (4). Practical implication: WP is not a magic shield. Labelling a letter does not make it privileged, and even a properly-footed letter can be admitted under an exception. Don't write anything you'd be embarrassed by if a judge reads it, and don't promise the client the letter is "safe" — the footing can fail.
The Calderbank offer (Calderbank v Calderbank [1976] Fam 93) lets a party put a settlement on the table that the court will see on costs at the end. Mostly displaced by CPR Part 36 in the civil courts, but still alive where:
Calderbank cost consequences in the civil courts are weaker than Part 36 — the court has discretion under CPR 44.2 and 36.17 does not apply. State the WPSATC footing explicitly; if uncertain, run the offer as a Part 36 instead.
Infer the intended footing from the request:
cpr-letter-drafter instead).Surface for confirmation only if ambiguous from the request.
Is there an existing or contemplated dispute? If no, WP doesn't apply — use open correspondence.
Use the appropriate template. Keep separate from any open correspondence going out the same day.
Flag any content that risks an Unilever exception (admissions, threats, signals of estoppel).
Produce the finished letter, not the template. Each section below is content to PRODUCE — render it as the completed correspondence, fully drafted on the chosen footing. Do not echo the template skeleton back to the user, and do not fabricate facts to fill a placeholder: for any value you don't have (sums, dates, party names, dispute description), insert [SOLICITOR: confirm X] rather than guessing. The placeholders below (£[X], [21] days, [brief description]) mark exactly the spots that must be confirmed, not copied verbatim.
The two structures below are the WP and WPSATC variants. Pick the one matching the confirmed footing and render only that.
WITHOUT PREJUDICE
[Date]
[Recipient]
Dear Sirs,
Re: [Matter — dispute description]
This letter is written without prejudice as a genuine attempt to settle the dispute between our respective clients concerning [brief description of the dispute].
This letter is intended to be confidential and may not be disclosed to the court without our written consent.
Yours faithfully,
[Signature]
WITHOUT PREJUDICE SAVE AS TO COSTS
[Date]
[Recipient]
Dear Sirs,
Re: [Matter]
This letter is written without prejudice save as to costs.
If the offer is not accepted, our client reserves the right to refer to this letter on the question of costs after judgment.
Yours faithfully,
[Signature]
[FOOTING — review: this content reads more open than WP][UNILEVER RISK — admission / threat / unambiguous impropriety language][SEPARATION — keep open correspondence in a different letter]Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take lawve-ai/without-prejudice-drafter-andrew-bird from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.