UK Legal Plugins

11 legal plugins built for UK jurisdiction — English & Welsh, Scottish, and Northern Irish law. Reviews, drafting, deadline tracking, investigations, diligence, and learning — wired to UK sources (BAILII, TNA Find Case Law, legislation.gov.uk, Companies House, GOV.UK, ICO, FCA, Hansard).

Works in any agent that supports the Open Plugins spec: Claude Code, Claude Cowork, Cursor, GitHub Copilot, and Codex.

New here? Start with QUICKSTART.md — install in 60 seconds. This README is the full reference.

[!IMPORTANT] Every output from these plugins is a draft for solicitor or barrister review — not legal advice, not a legal conclusion, not a substitute for a regulated lawyer. The skills are built with guardrails that reflect that: source attribution on every citation, conservative defaults on privilege and subjective legal calls, jurisdiction assumptions surfaced (E&W default, Scots/NI divergences flagged), and explicit gates before anything is filed, sent, or relied on. A regulated lawyer reviews, verifies, and takes professional responsibility for anything that leaves the building. These plugins make that review faster; they do not replace it.

Not affiliated with Anthropic. Not legal advice. SRA / BSB / CILEX regulated users remain responsible for compliance with their regulator's code of conduct. Where a skill includes a checklist, framework, risk flag, or characterisation of case law or regulatory guidance, that is an aid to the reviewing lawyer's own analysis — not a settled view of UK law.

Plugins

Agents

Each agent is named for the workflow it runs. Start with the ones that match your practice, then tune the underlying skill, the practice profile, and the connectors to how your team works.

Install

Claude Code

# 1. Add the marketplace
claude plugin marketplace add uk-agents/uk-legal-plugins

# 2. Install the plugin(s) you want
claude plugin install employment-legal-uk@uk-legal-plugins
claude plugin install commercial-legal-uk@uk-legal-plugins
claude plugin install privacy-legal-uk@uk-legal-plugins

# 3. Restart Claude Code. The plugin isn't live until you restart.

# 4. Run the cold-start interview
/employment-legal-uk:cold-start-interview

Or browse and install interactively with /plugins in a chat session.

To remove:

claude plugin uninstall employment-legal-uk          # remove a single plugin
claude plugin marketplace remove uk-legal-plugins    # remove the marketplace and all its plugins

Use user scope, not project scope. When asked, pick user scope. Project scope blocks the plugin from reading files outside the project folder — your contracts in Documents, your case bundle in Dropbox. User scope gives the plugin no extra file access; it just works from any folder. See QUICKSTART.md for details.

Claude Cowork

Add the marketplace (access all 11 plugins):

1. Personal plugins → Create plugin → Add marketplace → enter uk-agents/uk-legal-plugins
2. Plugins → Personal → click + next to each plugin you want

Or upload a single plugin (ZIP file):

1. Download the ZIP from the Releases page
2. Personal plugins → Create plugin → Upload plugin → select the ZIP

Agent compatibility

Getting started

Run the cold-start interview first. Every other skill in a plugin reads from the practice profile it writes. Skipping setup is the single most common reason a skill produces generic output.

/employment-legal-uk:cold-start-interview

Replace employment-legal-uk with whichever plugin you installed.

• Quick start (2 minutes) — role, practice setting, jurisdictional footprint. Skills run immediately with sensible defaults.
• Full setup (10–15 minutes) — your real termination triggers, seed documents, escalation matrix, integration checks. Sharper outputs.

The interview asks which at the start. You can upgrade any time with --full or re-run any section with --redo.

What it builds

A plain-text practice profile written to:

~/.claude/plugins/config/uk-legal-plugins/<plugin-name>/CLAUDE.md

Every skill reads this file before doing anything. It survives plugin updates and can be edited directly.

Shared company profile

The first plugin you configure saves your firm or company name, sector, jurisdiction list, and escalation chain to a shared profile:

~/.claude/plugins/config/uk-legal-plugins/company-profile.md

Every other plugin reads this and skips those questions — so setup gets faster as you add more plugins.

Connect a research tool

Pair with the UK Legal MCP server for live case law and legislation. Without it, every citation is tagged [model knowledge — verify]. See MCP Connectors below for the full list.

How it fits together

Everything is markdown and JSON. No build step.

MCP connectors

[!IMPORTANT] Connect the UK Legal MCP first. Without it, every citation comes from training data alone and is flagged [verify]. With it, the plugins pull from BAILII, TNA Find Case Law, legislation.gov.uk, and Hansard, and every citation is tagged with its source.

Each plugin's .mcp.json already lists the connectors it uses. You authorise them once, then Claude pulls from authoritative sources and verifies its citations against current databases.

See CONNECTORS.md for what makes a good legal MCP connector and how to submit one.

Making it yours

These are reference templates. They get better when you tune them to how your team works — and the customisation mechanism is the plugin itself, not a config file buried in a repo.

• Run the cold-start interview. It is the customisation mechanism. It asks how your practice works, reads your seed documents, and writes your practice profile. Every other skill reads from that profile.
• Edit the practice profile. Your profile at ~/.claude/plugins/config/uk-legal-plugins/<plugin>/CLAUDE.md survives plugin updates. Edit it directly for small fixes — a wrong escalation threshold, a new integration, a policy update.
• Re-run setup. /<plugin>:cold-start-interview again for a full re-interview when your practice shifts materially (new jurisdiction, new CLM, new policy).
• Swap connectors. Point .mcp.json at your CLM, DMS, eDiscovery platform, launch tracker, HRIS. Skills fall back gracefully when a connector isn't configured — no silent no-ops.
• Bring your playbook and templates. Drop your terminology, house style, and branded templates into the plugin's CLAUDE.md and references/.
• Fork skills for house style. Every skill is a markdown file under skills/. Edit the steps, the gates, the output format.

No build step. Everything is markdown and JSON.

Skill & command reference

The full map across all 11 plugins. The cold-start interview is the first thing to run in any plugin.

ai-governance-legal-uk

commercial-legal-uk

corporate-legal-uk

employment-legal-uk

ip-legal-uk

law-student-uk

legal-clinic-uk

litigation-legal-uk

privacy-legal-uk

product-legal-uk

regulatory-legal-uk

Repository layout

.claude-plugin/marketplace.json   # the marketplace manifest
<plugin>/                         # 11 plugins
  .claude-plugin/plugin.json      # plugin manifest
  .mcp.json                       # MCP servers the plugin connects to
  CLAUDE.md                       # practice-profile TEMPLATE (copied on cold-start)
  README.md                       # per-plugin docs
  skills/<name>/SKILL.md          # one skill per directory
  agents/<name>.md                # scheduled / event-driven agents
  hooks/hooks.json                # hook config (optional)
references/                       # shared templates (company profile, dashboard)

Each plugin's CLAUDE.md is a template — the cold-start-interview skill copies it to ~/.claude/plugins/config/uk-legal-plugins/<plugin>/CLAUDE.md on your machine.

Contributing

Everything here is markdown and JSON. Fork, edit, PR. See CONTRIBUTING.md.

• New skill → add <plugin>/skills/<skill-name>/SKILL.md with name, description, argument-hint frontmatter (description under 1024 chars). Invokable as /<plugin>:<skill-name>.
• New agent → add <plugin>/agents/<name>.md with scheduling frontmatter and a system prompt.
• New connector → see CONNECTORS.md for what makes a good legal MCP server and how to submit yours.
• Run validation before pushing → claude plugin validate .claude-plugin/marketplace.json and claude plugin validate <plugin>/.

License

Licensed under the Apache License, Version 2.0.

Credit

These plugins started as a UK-jurisdiction contribution to Anthropic's claude-for-legal (PR #46). This repo is the standalone home, maintained as a published product for UK legal professionals.

Not affiliated with Anthropic. Built by the community as a UK-jurisdiction contribution to the Open Plugins ecosystem.