Reviews or drafts the agreement that pays an employee to settle their claims — and flags the statutory conditions that decide whether it actually binds them. Works under s.203 ERA 1996 for England & Wales. Flags apparent s.203 condition gaps for a solicitor to confirm (writing, specific complaints, independent adviser, identification, insurance, statement of conditions), drafts the substantive terms (sum, tax characterisation, confidentiality, references, restrictive covenants, indemnities), and surfaces enforceability risks. Does not rule on validity and is not legal advice. Use when the user says 'review this settlement agreement', 'draft a settlement agreement', 'compromise agreement' (old term), or asks whether an agreement is binding.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill settlement-agreement-review-andrew-bird
A settlement agreement is the standard vehicle for compromising employment claims. It must comply with the conditions in s.203 ERA 1996 [CITE NEEDED — s.203 ERA 1996] (and equivalent provisions in other statutes — EqA 2010 s.144 [CITE NEEDED — s.144 EqA 2010], TULR(C)A 1992 s.288, etc.) to validly settle the statutory claims it purports to cover. Otherwise the employee remains free to bring a claim. This skill flags apparent gaps in those conditions; it does not rule on whether an agreement is valid — that is for a qualified adviser to confirm.
The other valid vehicle is an ACAS COT3 (recorded by the ACAS conciliator) — no s.203 conditions apply. COT3s are simpler; settlement agreements allow more bespoke terms.
As legal context: a genuinely missing condition is fatal — the agreement may still settle contract claims (which don't need s.203 compliance) but won't bar statutory ET claims. Do not treat your read of the conditions as a ruling. Flag any condition that looks missing or doubtful for a solicitor to confirm rather than declaring the agreement invalid.
[NOT TAX ADVICE — recompute, accountant sign-off]):[CITE NEEDED — s.135 ERA] — tax-free up to £30k [SME VERIFY — current £30k threshold], doesn't count to PENP).[CITE NEEDED — s.402B ITEPA 2003] — PENP regime).[CITE NEEDED — s.401-403 ITEPA 2003] [SME VERIFY — current £30k threshold], balance taxable as employment income.[CITE NEEDED — s.225 ITEPA 2003] — restrictive undertakings).[CITE NEEDED — Moorthy v HMRC]; HMRC position contested — [SME VERIFY — current HMRC view]).[SME VERIFY — typical £500-£750 plus VAT], paid direct to the adviser).[CITE NEEDED — s.43J ERA 1996]), HMRC, and court orders. Recent law has tightened on NDAs in discrimination/harassment cases — [CITE NEEDED — Victims and Prisoners Act 2024] [SME VERIFY — Victims and Prisoners Act 2024 NDA restrictions in regulated professions].Run through the s.203 checklist. Flag any condition that appears missing or doubtful for a solicitor to confirm. Do not declare the agreement valid or invalid — report apparent status only.
Walk through each substantive term against the checklist. Flag terms that are unusual, missing, or commercially adverse to the user's side.
Review the breakdown. If PILON is being paid, work the PENP formula as a cross-check only — [NOT TAX ADVICE — recompute, accountant sign-off] on the result and on every figure. PENP formula: (BP × D) / P — where BP = basic pay in pay period before notice, D = days in unworked notice, P = days in pay period [SME VERIFY — s.402D ITEPA formula and definitions]. Do not present the computed PENP or any net figure as authoritative; it is a prompt for an accountant.
Output either: (a) commented review with risk flags, or (b) clean draft.
Render the sections below as the finished review — do not echo this template back, and do not invent terms to fill a section; if the agreement is silent on a head, say so. Lead with the not-legal-advice line.
A reviewer-note line: *not legal advice; flags apparent issues only; verify with a solicitor before relying on anything below; this skill does not rule on the validity of the agreement.*
Apparent s.203 status (s.203 ERA / s.144 EqA) — a table of the six conditions, each marked Present / Apparently missing / Unclear, with a note. Then one line: Apparent status (verify with a solicitor): [conditions appear satisfied / [N] condition(s) appear missing — confirm with a solicitor]. Never state "Valid" or "Invalid".
The conditions to check:
Substantive review — a table by clause (payment breakdown, confidentiality, reference, warranties, restrictive covenants, claims schedule, tax indemnity): position, risk to the user's side, suggested change.
Tax analysis — every figure carries [NOT TAX ADVICE — recompute, accountant sign-off]. Cover PILON / PENP, s.401-403 ITEPA treatment, other heads, and any net-to-employee estimate — all as prompts for an accountant, never as authoritative figures.
Recommended changes — numbered list of specific edits in priority order.
Markers used inline as you go:
[CONDITION GAP — flag for solicitor to confirm] — a s.203 condition that appears missing or doubtful (not a ruling that the agreement is invalid).[NOT TAX ADVICE — recompute, accountant sign-off] — on every tax figure.[CITE NEEDED — authority] — a statute or case referenced without a verified citation.[SME VERIFY — item] — a threshold, market figure, or contested position counsel should confirm (e.g. HMRC view on injury-to-feelings tax; Victims and Prisoners Act 2024 NDA restrictions; PENP figures).[CITE NEEDED — s.203(3A) ERA 1996].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/settlement-agreement-review-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.