克劳德（法律事务）

Claude for Legal

Reference agents, skills, and data connectors for the legal workflows we see most — in-house commercial, privacy, product, corporate, employment, litigation, regulatory, AI governance, IP, and the learning side of the practice (law school clinics and students).

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

Everything here is available two ways from one source: install it as a Claude Cowork or Claude Code plugin, or deploy it through the Claude Managed Agents API behind your own workflow engine. Same system prompt, same skills — you choose where it runs.

Getting started in Cowork

• Install Claude Desktop
• Get access to Claude Cowork
• Follow the instructions in the video below:

[!IMPORTANT] Every output from these plugins is a draft for attorney review — not legal advice, not a legal conclusion, not a substitute for a lawyer. They are built with guardrails that reflect that: source attribution on every citation, conservative defaults on privilege and subjective legal calls, jurisdiction assumptions surfaced, and explicit gates before anything is filed, sent, or relied on. A lawyer reviews, verifies, and takes professional responsibility for anything that leaves the building. These plugins make that review faster; they do not replace it.

These plugins do not represent Anthropic's legal positions. They are tools that help lawyers analyze issues. Where a skill includes a checklist item, a suggested framework, a risk flag, or a characterization of case law or regulatory guidance, that is an aid to the reviewing attorney's own analysis, not a statement of Anthropic's view of the law. The law in many of these areas is unsettled and evolving. The attorney using the plugin — not the plugin, and not Anthropic — is responsible for the legal positions taken in their work product.

What's in the repo:

• Practice-area plugins covering in-house, firm, and academic legal work — each one built around a cold-start interview that learns your playbook and a CLAUDE.md practice profile that every skill reads from.
• Managed-agent cookbooks for the scheduled, eyes-on-the-feed workflows (renewal watcher, docket watcher, regulatory feed monitor, diligence grid, launch radar).
• MCP connectors across general productivity (Slack, Google Drive, Box) and legal-specific systems (Ironclad, DocuSign, iManage, Everlaw, CourtListener, and more).
• Named agents — end-to-end workflow agents (Vendor Agreement Reviewer, DSAR Responder, Termination Reviewer, Claim Chart Builder, …) with job-style names and a single command to run each one.

Agents

Each agent is named for the workflow it runs. They're the most common surface — start with the ones that match your work, then tune the underlying skill, the practice profile, and the connectors to how your team does it.

The trust layer for community legal skills

The community is building legal skills fast — registries like LegalOps Consulting's lpm-skills and Lawvable already list dozens. But nobody certifies community skills, and a lawyer installing a random skill from GitHub is installing code that runs with access to their matter files, their practice profile, and their research connectors.

legal-builder-hub gives the ecosystem the trust layer it's missing:

• Security review — hidden-content scan, injection detection, structural trust check on every install
• Allowlist — restrictive-by-default source gate (registries, publishers, connectors, licenses)
• License gate — deployment-context-aware license policy (personal / firm-internal / product-embedding)
• Freshness gate — tracks whether bundled reference content (regulations, statutes, procedures) has passed its verification window, and warns at invocation
• Re-scan at update — a skill that was clean at v1.0 and poisoned at v1.1 gets caught
• Install log — an auditable record of what's installed, from where, under what license, with what review verdict

The allowlist is restrictive by default. Permissive mode is an explicit choice. A non-lawyer gets routed to their attorney contact, not an "install anyway" button.

Community skills go through the same design review (/legal-builder-hub:skills-qa) as the first-party plugins. If you build for lawyers, run the QA against your own skill before publishing. It's the review a lawyer would do if they could read code.

Building a connector? See CONNECTORS.md for what a good legal MCP server looks like and how to submit yours for inclusion.

Claude for Microsoft 365

Lawyers live in Word and Excel. Every contract-touching skill in this repo is authored to work in the Claude for Word sidebar, with tracked changes as the output mode. That's commercial-legal:review (vendor agreements, NDAs, SaaS subscriptions), commercial-legal:amendment-history, ip-legal:ip-clause-review, ai-governance-legal:vendor-ai-review, privacy-legal:dpa-review, and the diligence extraction in corporate-legal. A reviewer accepts or rejects each change exactly as they would for a human markup — numbering, defined terms, cross-references, and styles are preserved.

The Excel-facing skills produce workbooks that open cleanly: corporate-legal:tabular-review writes a multi-sheet .xlsx with a sources sheet, litigation-legal:claim-chart writes an element-by-element claim chart with citation columns, corporate-legal:entity-compliance writes the compliance register with deadline columns, and commercial-legal:renewal-tracker exports the renewal register sorted by cancel-by date.

Install Claude for Microsoft 365 from Microsoft AppSource. Once installed, the skills from any plugin you've enabled are available from the sidebar via /, and connectors are reachable from the same surface. A single thread can span Word, Excel, PowerPoint, and Outlook.

For IT admins deploying the add-in against your own cloud (Vertex AI, Bedrock, or an internal gateway) rather than Anthropic's API, see the separate claude-for-msft-365-install tooling.

Making It Yours

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

• Run the cold-start interview. It is the customization mechanism. It asks how your practice works, reads your seed documents, and writes your practice profile. Every other skill reads from that profile. A /commercial-legal:cold-start-interview with five signed MSAs, your playbook, and your escalation matrix will make the review skills noticeably sharper.
• Edit the practice profile. Your profile lives at ~/.claude/plugins/config/claude-for-legal/<plugin>/CLAUDE.md. Edit it directly for small fixes — a wrong escalation threshold, a new integration, a policy update. It survives plugin updates.
• 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, e-discovery 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/. The skills will pick them up.
• Fork skills for house style. Every skill is a markdown file under skills/. Edit the steps, the gates, the output format.
• Add scheduled agents. The agents under <plugin>/agents/ are markdown with a cron-style schedule. Add your own for the watchers your team needs.

No build step. Everything is markdown and JSON.

Skill & Command Reference

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

ai-governance-legal

legal-builder-hub

legal-clinic

commercial-legal

corporate-legal

employment-legal

ip-legal

litigation-legal

privacy-legal