Claude for Legal: a reference plugin for common legal workflows

Who it's for

Use this plugin set when you handle the legal workflows the notes name — in-house commercial, privacy, product, corporate, employment, litigation, regulatory, AI governance, IP, plus law-school clinics and student-side learning — and you need reference agents, skills, and data connectors. It is a reference implementation, not a law-firm opinion letter.

Hard precondition: every plugin output is a draft for attorney review, not legal advice, not a legal conclusion, and not a substitute for a lawyer. If no attorney will read the draft, do not send any of its text outward.

The main access path is written in QUICKSTART.md and claims 60 seconds. The same source can also install as a Claude Cowork or Claude Code plugin, or deploy via the Claude Managed Agents API onto your own workflow engine. Take only QUICKSTART first; do not open all three paths at once.

First try in 3 minutes

Official page:

https://github.com/anthropics/claude-for-legal

Open QUICKSTART.md in the repository first and follow its 60-second install. Do not write a separate install command. The notes give no copyable install line in the excerpt; commands follow QUICKSTART. Before install, confirm the current environment is Claude Cowork or Claude Code (API deploy is another path; do not use it the first time).

Install changes plugin state. Read QUICKSTART, then run it; after install, first check whether the plugin appears. The first time, do not run an agent that would write a memo.

Success signal: after QUICKSTART finishes, you can see this legal plugin set in the current Claude environment, and you know every later output is only a draft. If QUICKSTART fails, stop; do not add an installer that never appeared.

If you want to try a named agent immediately, prepare your own vendor playbook first, then consider /commercial-legal:review. That will check a vendor MSA against the playbook and produce a redline memo — confirm the memo may be written, then run it, then open the file and check it matches your playbook points.

Use cases

Case 1: Connect the plugin via QUICKSTART. Open QUICKSTART.md and finish that 60-second install in Claude Cowork or Claude Code. Confirm the plugin is visible. The same source can go through the Managed Agents API, but that is a deploy “behind your own workflow engine”; do not mix it in the first time, and the notes give no API call example.

Case 2: Vendor Agreement Reviewer. The notes' invoke is /commercial-legal:review: check a vendor MSA against your playbook and produce a redline memo. This writes a file. First confirm the MSA and playbook are in the workspace and the memo may land, then run; open the memo immediately and check it actually follows the playbook. Do not apply this command to unnamed agreement types.

Boundaries

Every output is only a draft for an attorney to read, not legal advice, and not a substitute for a lawyer.

The main path is QUICKSTART.md. Visible text has no concrete install command; do not invent one.

Install surfaces named are Claude Cowork, Claude Code plugins, and the Claude Managed Agents API; do not infer that only one of them works, and do not add steps for unnamed clients.

Named agents are evidenced only as Vendor Agreement Reviewer and /commercial-legal:review. Other practice lines appear only on the roster, with no commands; do not invent slash invokes.

The notes give no language coverage or pricing. Keep undocumented items unknown.