customize · anthropics/claude-for-legal, ip-legal — Claude Code skill: IP profile setup
The customize Claude Code skill updates selected settings in an IP practice profile. It runs when asked to edit the profile, risk posture, contacts, or review rules.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install ip-legal@claude-for-legalWhat customize does
The skill shows the current IP practice settings and changes one selected value. It covers practice scope, risk posture, escalation contacts, portfolio, brand protection, OSS review rules, and matter workspace paths. After confirming the new value, it writes the change to the configuration.
A configured profile is required. The skill reads ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md and ~/.claude/plugins/config/claude-for-legal/company-profile.md. If the files are missing or still contain [PLACEHOLDER], run /ip-legal:cold-start-interview first. Changes to shared company details affect all 12 plugins.
What it helps with
- change risk posture without repeating the initial interview
- update contacts for IP escalations
- revise the IP practice scope or portfolio
- add an OSS license review rule
Example prompts for the agent
- Change the IP profile's risk posture to conservative.
- Update the escalation contacts for trademark matters.
- Add this license to the OSS review blocklist.
How to install customize
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install ip-legal@claude-for-legalThis installs the whole ip-legal plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill customize -a claude-code3Manually: put the files in place
~/.claude/skills/customize/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/customize/
1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill customize -a codex2Manually: put the files in place
.agents/skills/customize/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill customize -a cursor2Manually: put the files in place
.cursor/skills/customize/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-for-legal ip-legal/skills/customize2Manually: put the files in place
.github/skills/customize/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-for-legal --skill customize -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-for-legal --path ip-legal/skills/customizeManually: put the files in place
.devin/skills/customize/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about customize
How do I install customize in Claude Code?
Run /plugin marketplace add anthropics/claude-for-legal, then /plugin install ip-legal@claude-for-legal.
What does customize do?
It lets you edit one setting in an IP practice profile. The skill shows the current value, asks for the replacement, and writes it after confirmation.
What does customize need to work?
The profile must be set up with /ip-legal:cold-start-interview. The skill reads ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md and ~/.claude/plugins/config/claude-for-legal/company-profile.md.
Source text
SKILL.md · Apache-2.0
---
name: customize
description: >
Guided customization of your IP practice profile — change one thing without
re-running the whole cold-start interview. Adjust risk posture, escalation
contacts, portfolio scope, brand protection strategy, enforcement posture,
clearance thresholds, OSS review rules, or matter workspace paths. Use when
the user says "change my [thing]", "update my profile", "edit my config",
or "customize".
argument-hint: "[section name, or describe what you want to change]"
---
# /customize
## When this runs
The user typed `/ip-legal:customize`. They want to change something in their
practice profile — a risk posture, an escalation contact, a portfolio
position, an enforcement tactic — without re-running the whole cold-start
interview and without hand-editing YAML.
## What to do
1. **Read the config.** Read
`~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md`
(and `~/.claude/plugins/config/claude-for-legal/company-profile.md` one
level up). If the plugin config does not exist or still contains
`[PLACEHOLDER]` values, say:
> You haven't run setup yet. Run `/ip-legal:cold-start-interview` first —
> customize is for adjusting a profile you already have.
2. **Show the customizable map.** List what's in the profile, grouped, with a
one-line summary of the current value:
- **Company / who you are** — name, industry, jurisdictions, stage, practice
setting *(shared across all 12 plugins — changes flow through
`company-profile.md`)*
- **IP practice profile** — which IP types are in scope (patent,
trademark, copyright, trade secret, design), practice orientation
(prosecution / transactions / enforcement / in-house portfolio)
- **Risk posture** — conservative / middle / aggressive, what each means
for clearance thresholds, FTO opinions, and cease-and-desist escalation
- **People** — IP counsel, outside firms by IP type, enforcement
escalation chain, invention committee
- **Portfolio** — patent families, trademark classes, key marks, countries
of registration, watch services
- **Brand protection** — enforcement posture on marketplace takedowns,
domain squatters, parody / fair use calls
- **Enforcement posture** — when to send C&D vs. cure letter vs. suit;
escalation triggers by infringement type
- **Clearance and FTO** — search vendors, clearance confidence thresholds,
FTO opinion format
- **OSS review** — license tier policies, ship-blocker licenses, review
cadence for new dependencies
- **Workflow** — matter workspaces (matter IDs, family IDs), docket feed,
invention intake form
- **Integrations** — patent docket system / trademark office connectors /
Slack / document storage status, fallbacks
3. **Ask what they want to change.**
> What would you like to adjust? Pick a section, or describe the change in
> your own words.
4. **Make the change.** Show the current value, ask for the new value, explain
what changes downstream, confirm, write it to the config.
Examples:
- *Adding a new trademark watch class:* "`/portfolio` will include class
XX in watch reports and `/infringement-triage` will route class-XX
findings accordingly."
- *Enforcement posture aggressive → middle:* "`/cease-desist` will offer
cure-letter drafts as a first option for ambiguous cases instead of
going straight to C&D."
- *New ship-blocker OSS license:* "`/oss-review` will fail reviews that
include this license rather than warning."
5. **For shared-profile changes** (company name, industry, jurisdictions,
practice setting, stage): write to
`~/.claude/plugins/config/claude-for-legal/company-profile.md` and note:
> This change affects all 12 plugins — any plugin that reads your
> jurisdiction footprint now sees [new value].
6. **Close.**
> Done. Your next output will reflect the change. Anything else? You can
> run `/ip-legal:customize` anytime.
## Guardrails
- **Never delete a section.** If the user wants to "remove" an IP type from
scope, set it to `[Not currently in scope]` and explain what drops out.
- **Flag internal inconsistency.** If the change would make the profile
inconsistent (e.g., trademark out of scope + trademark watch service
configured; or aggressive enforcement posture + "all C&Ds go to outside
counsel"), flag the tension.
- **Flag guardrail degradation.** The `[review]` flag, source attribution
tags, and `[verify]` tags on cited authorities are load-bearing — do not
remove. Clearance confidence is load-bearing on `/clearance` output — do
not suppress.
- **One change at a time.** Don't re-ask the whole interview.
© Anthropic · Apache-2.0 · anthropics/claude-for-legal
Similar skills
All skills for Finance and business →customize by other authors comes first.