Skip to main content
plugin official · Anthropic

ip-legal — Claude Code plugin: features and setup

The ip-legal Claude Code plugin handles first-pass intellectual property work, from trademark screening to renewal tracking. A setup interview records the practice profile before other tasks begin.

Apache-2.0 ★ 10,060 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-for-legal
/plugin install ip-legal@claude-for-legal
Open on GitHub

What ip-legal does

ip-legal prepares draft work and initial reviews across intellectual property matters. It screens proposed marks and freedom to operate, reviews invention disclosures, handles cease-and-desist and DMCA notices, checks contract clauses and open-source licenses, and tracks registrations and renewal dates.

At first use, an interview gathers practice areas, jurisdictions, approval rules, and portfolio details. The resulting profile is saved as ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md, a document that can be edited directly. A research tool supports citation checks; the plugin also runs without one, tagging citations [verify].

A lawyer must review the output; it is not a legal conclusion. The plugin does not draft patent claims. Its patent work covers initial patentability screening and the other listed review tasks. Sending or filing materials and other consequential actions require explicit confirmation.

What it helps with

  • screen a proposed trademark before use
  • flag patents that may block a product
  • review an invention disclosure for initial patentability
  • check a repository for open-source license obligations
  • track registrations and renewal deadlines

Example prompts for the agent

  • Screen the proposed Acme trademark before launch.
  • Triage freedom to operate for this product and claim scope.
  • Check the repository for open-source license obligations.

How to install ip-legal

Plugin marketplace

/plugin marketplace add anthropics/claude-for-legal
/plugin install ip-legal@claude-for-legal

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about ip-legal

How do I install ip-legal in Claude Code?

Run these commands in order: /plugin marketplace add anthropics/claude-for-legal, then /plugin install ip-legal@claude-for-legal.

What does ip-legal do?

It prepares initial reviews for trademark and patent matters, DMCA notices, contract clauses, and open-source licenses, and keeps track of registrations. A lawyer reviews its drafts.

Does ip-legal need a research tool?

No. It can run without one, but citations are marked [verify]; connecting a research tool enables citation checks.

Source text

ip-legal · Apache-2.0
# IP Counsel Plugin

Intellectual property practice: trademark, copyright, patent, trade secret, and open source. Drafts and triages cease-and-desist letters and DMCA takedowns (sending and responding), runs first-pass trademark clearance and freedom-to-operate triage, reviews IP clauses in agreements, tracks registrations and renewal deadlines, and checks open source license compliance. Built around a practice profile that gets written by a cold-start interview — the plugin learns *your* enforcement posture, portfolio, and approval matrix, not a generic one.

**Every output is a draft for attorney review — cited, flagged, and gated — not a legal conclusion.** The plugin does the work: reads the documents, applies your playbook, finds the issues, drafts the memo. A lawyer reviews, verifies, and decides. Citations are tagged by source so you know which ones came from a research tool and which ones need checking. Privilege markers are applied conservatively so nothing waives by accident. Consequential actions — filing, sending, executing — are gated behind explicit confirmation.

## Who this is for

| Role | Primary workflows |
|---|---|
| **In-house IP counsel** | Enforcement decisions, clause review, portfolio oversight, FTO triage |
| **IP paralegal / specialist** | Portfolio and renewal tracking, clearance first passes, matter intake |
| **Brand protection manager** | Cease-and-desists, DMCA takedowns, watch-service follow-up |
| **IP prosecutor (TM / copyright)** | Clearance, clause review, portfolio maintenance — *not patent claim drafting* |
| **Law firm IP associate** | Matter workspaces per client, clearance and FTO triage, clause review |
| **Legal ops managing an IP portfolio** | Registration tracker, renewal deadlines, OSS compliance checks |

This plugin does **not** draft patent claims. Patent prosecution with claim strategy is a specialist craft that needs a patent agent or patent attorney and should not be outsourced to a generalist tool. Patent work here is limited to FTO triage (is this product blocked by someone else's patent?), IP clause review in agreements, portfolio renewal tracking, and infringement triage.

## First run: the cold-start interview

On first use, the plugin interviews you — ten to fifteen minutes, conversational — to learn how your practice actually works. It asks about your practice area mix, your jurisdiction footprint, your enforcement posture, your approval matrix, and your escalation triggers. Then it asks for your portfolio list, brand guidelines, C&D templates, enforcement playbook, and OSS policy — whatever you have — so it can extract rather than making you re-type.

It writes what it learns to `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` — a plain-English document about your practice that every other skill reads before doing anything. You edit the document, not a config file.

```
/ip-legal:cold-start-interview
```

**Practice area mix.** Early in setup, you'll be asked which IP areas you actually work in — trademark, patent, copyright, trade secret, open source, or all. The plugin skips questions in areas you don't practice. Your configuration can hold multiple areas in parallel, and each skill asks which area applies when it's not obvious from what you paste.

**Enforcement posture.** You'll be asked where you land on the aggressive / measured / conservative spectrum for sending assertion letters, and who approves sending each letter type. The posture flips the defaults of the cease-and-desist, takedown, and infringement-triage skills.

## Commands

| Command | Does |
|---|---|
| `/ip-legal:cold-start-interview` | Run (or re-run) the cold-start interview |
| `/ip-legal:cease-desist [context]` | Cease-and-desist — send, or triage an inbound one, with the approval routing your CLAUDE.md requires |
| `/ip-legal:takedown [context]` | DMCA takedown — send, respond to a received notice, or draft a counter-notice |
| `/ip-legal:clearance [mark]` | First-pass trademark clearance — knockout + confusion analysis, attorney still signs off |
| `/ip-legal:fto-triage [product / claim scope]` | Freedom-to-operate triage — surfaces blocking references for attorney review |
| `/ip-legal:invention-intake [disclosure]` | Invention disclosure first-pass screen — novelty, obviousness, §101, bar dates, detectability, strategic value |
| `/ip-legal:infringement-triage [context]` | Infringement triage — is this worth pursuing, and how |
| `/ip-legal:ip-clause-review [file]` | Review IP clauses in an agreement — assignment, license grant, IP indemnity, OSS reps |
| `/ip-legal:oss-review [repo / file list]` | Open source license compliance check — copyleft obligations, attribution, license compatibility |
| `/ip-legal:portfolio` | Registration and renewal tracker — what's due, what's filed, what needs action |
| `/ip-legal:matter-workspace` | Manage matter workspaces (multi-client private practice only) — new, list, switch, close, none |

## Skills

| Skill | Purpose |
|---|---|
| **cold-start-interview** | First-run interview that writes `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` |
| **cease-desist** | Draft or triage a C&D; routes through the approval matrix before sending |
| **takedown** | DMCA notice, response to a received takedown, or counter-notice |
| **clearance** | Knockout search + likelihood-of-confusion first pass for a proposed mark |
| **fto-triage** | FTO triage — flags references an attorney should read before launch |
| **invention-intake** | First-pass patentability screen for an invention disclosure — novelty, obviousness, §101, bar dates, detectability, strategic value |
| **infringement-triage** | Given an apparent infringement, decide: ignore / soft letter / C&D / file |
| **ip-clause-review** | Reviews IP clauses in MSAs, SOWs, licenses, contractor agreements |
| **oss-review** | Checks open source licenses in a repo against the OSS policy |
| **portfolio** | Registration register, renewal deadlines, status dashboard |
| **matter-workspace** | Create, list, switch, and close matter workspaces for multi-client practices; isolates each client/matter so context does not leak across them |

## Interactive commands vs. scheduled agents

The commands above run when you invoke them — for when you're working a matter. The agents below run on a schedule — for what moves while you're not looking:

| Agent | What it watches | Default cadence |
|---|---|---|
| **ip-renewal-watcher** | Portfolio register — computes what's due (renewals, affidavits, maintenance) in the next 90 days and posts a ranked deadline report | Weekly |

## Connectors and citation verification

**Connect a research tool first — the citation guardrails depend on it.** Without one, every cite is tagged `[verify]` and the reviewer note above each deliverable records that sources weren't verified. The plugin works either way; it just does more of the verification for you when a research tool is connected.

The legal research connectors in this plugin aren't just data sources — they're the difference between a verified citation and a citation you have to check. A citation retrieved through **CourtListener** (U.S. court opinions, PACER dockets, citation verification) or **Descrybe** (primary-law search, citation treatment, quoted-language verification) is tagged with its source and can be traced back. A citation from the model's knowledge or from web search is tagged `[verify]` or `[verify-pinpoint]` and should be checked against a primary source before anyone relies on it. The plugin tiers its citations so your verification time goes where it matters.

## Integrations

Ships with connectors configured in `.mcp.json`:

- **Solve Intelligence** — patent and non-patent literature search, SEP technical standards, prior art, claim analysis
- **CourtListener** — U.S. court opinions, PACER dockets, citation verification
- **Descrybe** — primary law research by concept or wording, citation treatment, quoted-language verification
- **Slack** — search messages, read channels, find discussions
- **Google Drive** — search, read, and fetch documents

With patent research connected: FTO and prior-art skills pull references automatically instead of relying on user-supplied lists.

With a case-law tool connected: clearance and infringement-triage skills verify precedent and check whether a cited case is still good law.

With Drive or Slack connected: portfolio exports, C&D templates, and enforcement-log updates route through the channel you pointed us at.

## Quick start

### 1. Get interviewed

```
/ip-legal:cold-start-interview
```

Ten to fifteen minutes. Have your portfolio list, brand guidelines (if any), a C&D template (if any), and your OSS policy (if any) ready to share.

Your configuration is stored at `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` and survives plugin updates.

### 2. Clear a mark

```
/ip-legal:clearance "APEXLEAF"
```

Output: knockout-hit list, likelihood-of-confusion factor analysis, flags for attorney review. Not a go/no-go.

### 3. See what's due

```
/ip-legal:portfolio
```

Output: registrations with renewal, affidavit, or maintenance deadlines in the next 90 days, grouped by urgency.

## File structure

```
ip-legal/
├── .claude-plugin/plugin.json
├── .mcp.json
├── CLAUDE.md                    # Your practice profile — written by cold-start, edited by you
├── README.md
├── agents/
│   └── ip-renewal-watcher.md
├── skills/
│   ├── cold-start-interview/
│   ├── cease-desist/
│   ├── takedown/
│   ├── clearance/
│   ├── fto-triage/
│   ├── invention-intake/
│   ├── infringement-triage/
│   ├── ip-clause-review/
│   ├── oss-review/
│   ├── portfolio/
│   └── matter-workspace/
└── hooks/hooks.json
```

## Configuration

The plugin reads user-specific configuration from:

```
~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md
```

This path survives plugin updates. The `CLAUDE.md` that ships with the plugin is a template — it is replaced every upgrade. The cold-start interview writes your populated version to the config path above; from then on, edit that file directly when something changes.

## How it learns

Your practice profile at `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` isn't static — it improves as you use the plugin. Skills tell you when an output used a default you should tune. The `ip-renewal-watcher` agent tracks the portfolio register and surfaces upcoming renewal deadlines at your cadence. You can re-run setup, edit the file directly, or tell a skill to record a new position.

## Notes

- Every skill reads the practice profile first. If it finds placeholders, it stops and tells you to run `/ip-legal:cold-start-interview`. There's no generic fallback — a generic IP posture is worse than no posture.
- Sending a C&D starts a fight. The `/ip-legal:cease-desist` skill will not send anything itself; it drafts, surfaces the approval matrix entry, and waits for the approver.
- `/ip-legal:clearance` and `/ip-legal:fto-triage` are **first-pass** triage. The output is a research package for an attorney, not a clearance opinion. The skill says so on every run.
- `/ip-legal:oss-review` flags license obligations and incompatibilities. It does not bless a commercial-use decision — engineering and legal decide that together.
- Patent claim drafting is intentionally out of scope. This plugin plays well alongside a patent prosecution specialist; it does not replace one.

© Anthropic · Apache-2.0 · anthropics/claude-for-legal

Similar plugins

All plugins for Security →
linkfox-ruiguan-trademark-graphic-detection linkfox-ai linkfox-ruiguan-trademark-graphic-detection — a skill for Claude Code detects graphic trademarks and logos in product photos, then searches for similar registered marks. It runs during pre-listing image risk checks. CX Codex +1 230installs linkfox-ruiguan-text-trademark-detection linkfox-ai linkfox-ruiguan-text-trademark-detection — a skill for Claude Code and Codex that screens product titles, descriptions, and keywords for text trademark matches. It checks target sales regions before a listing goes live. CX Codex +1 235installs patent-application-creator RobThePCGuy patent-application-creator is a Claude Code skill that turns codebases or raw notes into a filing-ready provisional patent package. It halts drafting early when the invention is not commercially viable. CX Codex +1 837installs patent-drafting omer-metin patent-drafting — a skill for patent work: drafts claims, analyzes prior art, and responds to USPTO office actions. Grounded in reference guides covering claim strategy, specification requirements, and USPTO practice. CX Codex +1 160installs legal-advisor VoltAgent Community legal-advisor is a Claude Code subagent that reviews contracts, compliance requirements, and legal risks for technology businesses. It also helps draft service terms and IP materials. CX Codex 1,776installs takedown lawyerd999 Identifies the true host behind CDN proxies and outlines DMCA takedown routes directly inside your AI workflow. CX Codex +1 ★ 11repo stars

From the same set174

The whole set →
renewal-watcher The renewal-watcher Claude Code subagent checks a contract renewal register and posts upcoming dates. It runs weekly by default or on request, sending its report to a configured channel. CX Codex ★ 10,060repo stars playbook-monitor playbook-monitor — a subagent for Claude Code and Cursor that watches the deviation log and proposes playbook updates when clause positions change. CX Codex ★ 10,060repo stars deal-debrief The deal-debrief subagent for Claude Code finds signed agreements that depart from a legal playbook. It runs on a schedule or when asked to review recent deals. CX Codex ★ 10,060repo stars cocounsel-legal cocounsel-legal is a Claude Code plugin that searches Westlaw Deep Research and Practical Law for legal research, then generates reports citing U.S. federal and state authorities. ★ 10,060repo stars legal-builder-hub legal-builder-hub — a Claude Code plugin that discovers, audits, and installs community legal skills from GitHub registries. Blocks unverified skill files until explicit manual approval. ★ 10,060repo stars legal-clinic The legal-clinic Claude Code plugin configures a law school clinic and supports supervised student casework. It prepares drafts and tracks deadlines; it does not decide whether to accept a case or file documents. ★ 10,060repo stars law-student law-student — a plugin for Claude Code provides Socratic drilling and legal exam preparation. Runs during case briefing, outline drafting, and IRAC essay reviews. ★ 10,060repo stars litigation-legal litigation-legal — a plugin for Claude Code organizes litigation matters, tracks dispute portfolios, and drafts legal documents for attorney review. Handles intake logs, chronologies, legal holds, and outside counsel updates. ★ 10,060repo stars

Project sponsors

Companies that keep this analytics open