$ loading_
Termination review — high-risk flag detection, severance + release, and final pay timing by jurisdiction. Jurisdiction-specific rules and release consideration periods are researched per review, not stored. Use when the user says "reviewing a termination", "can we fire this person", "term review", or describes a termination scenario.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "termination-review" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/employment-legal/skills/termination-review/SKILL.md 2. Save it as ~/.claude/skills/termination-review/SKILL.md 3. Reload skills and tell me it's ready
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → termination review triggers, high-risk flags, severance practice, jurisdiction rules.Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /employment-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/employment-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Most terminations are fine. A few are lawsuits waiting to happen. This skill runs the checklist that catches the second kind before the decision is final. The skill does not state the law — every jurisdiction-specific rule and release-period requirement is researched and cited at the time of review.
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → termination review triggers, high-risk flags, standard severance,
jurisdiction table.
Prepend the work-product header from ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → ## Outputs (it differs by user role — see ## Who's using this). Match the memo format from seed term memos referenced in that config where one exists. The work-product header is always first.
This is the most important step. Check every flag from ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md. Default
set:
| Flag | Why it's high-risk | Check |
|---|---|---|
| Recent complaint | Retaliation claim | Has this employee filed any complaint (HR, ethics hotline, regulatory) recently? |
| Protected leave | Leave-law interference/retaliation | Currently on or recently returned from protected leave (FMLA/state equivalents, disability, parental, military)? |
| Protected class + timing | Discrimination claim | Protected class AND recently disclosed/visible (pregnancy announcement, religious accommodation request, disability disclosure)? |
| Whistleblower | Federal and state whistleblower statutes | Has this employee raised concerns about illegality, safety, fraud? |
| Thin documentation | "Why now?" problem | For performance terms: is there a PIP, written warnings, documented feedback? Or did this come out of nowhere? |
| Comparator problem | Disparate treatment | Is someone else doing the same thing and not being terminated? |
| Contract/handbook promise | Breach | Does the offer letter, handbook, or any writing promise a process that isn't being followed? |
| Exempt misclassification | FLSA + state wage claim with liquidated damages | See the classification check below. Fires on state + classification + title. |
Exempt/non-exempt classification flag. Fire this flag when ALL of the following are true:
…
Ask questions against an open investigation log — what witnesses said, where accounts conflict, what gaps exist, what the strongest evidence is on each issue. Use when the attorney needs to query the investigation record without re-reading every entry.
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your governance positions; flag training-on-data, liability, model changes, and AI policy consistency. Use when user says "review this AI agreement", "check OpenAI terms", "what did we agree to with [vendor]", "vendor sent an AI addendum", "is this AI contract okay", or attaches vendor AI terms.
Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, and draft the ask. Use when the user says "who needs to approve this", "escalate this", "does this need GC sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent counsel review. This skill never concludes a product is clear to launch.