customize · anthropics/claude-for-legal, litigation-legal — Claude Code skill: profile edits
The customize Claude Code skill edits individual settings in a litigation practice profile. It runs when someone asks to update the profile or change a specific setting.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install litigation-legal@claude-for-legalWhat customize does
The skill changes a litigation practice profile without repeating the initial interview or editing YAML by hand. It displays the current values, collects a replacement, explains which connected commands will be affected, asks for confirmation, then writes the change to the config. Each run handles one change.
Settings cover practice role, plaintiff or defense side, risk thresholds, document style, escalation contacts, and matter workspace paths. Changes to company details, industry, jurisdictions, or practice setting go into a shared profile and affect all 12 plugins. The profile must first be created with /litigation-legal:cold-start-interview; the skill preserves profile sections and guardrail flags.
What it helps with
- switch a practice profile from plaintiff to defense
- adjust the high-risk threshold for new matters
- revise the house style for legal documents
- add an escalation contact for a matter type
Example prompts for the agent
- Change my practice side to defense.
- Update the high-risk threshold for new matters.
- Add an escalation contact for intellectual property matters.
How to install customize
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install litigation-legal@claude-for-legalThis installs the whole litigation-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 litigation-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 litigation-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?
Add the marketplace with /plugin marketplace add anthropics/claude-for-legal, then install the plugin with /plugin install litigation-legal@claude-for-legal.
What does customize do?
It guides a single edit to a litigation practice profile. The skill shows the current setting, collects and confirms a replacement, then saves it to the config.
What does customize need to work?
Create the profile first by running /litigation-legal:cold-start-interview. If the config is missing or still has [PLACEHOLDER] values, the skill directs you to that command.
Source text
SKILL.md · Apache-2.0
---
name: customize
description: >
Guided customization of your litigation practice profile — change one thing
without re-running the whole cold-start interview. Adjust practice role,
side (plaintiff / defense / mixed), risk calibration, landscape, house
style, escalation contacts, severity vocabulary, 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 `/litigation-legal:customize`. They want to change something
in their litigation profile — a risk calibration, a house style rule, an
escalation contact, a landscape note — 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/litigation-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 `/litigation-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`)*
- **Practice role** — in-house counsel / outside counsel / solo / clinic
- **Side** — plaintiff / defense / mixed, and any posture nuances (class
action defense, regulatory enforcement defense, commercial
plaintiff, etc.)
- **Risk calibration** — what counts as high / medium / low risk on an
inbound demand, subpoena, or new matter; escalation triggers
- **Landscape** — regular adversaries, friendly and unfriendly venues,
judges to know, standing OC relationships
- **House style** — brief style, declaration format, demand letter
template, deposition outline structure, legal hold template
- **Severity vocabulary map** — how you translate severity labels across
client / internal / court-facing outputs
- **People** — matter leads, in-house team, outside counsel by matter
type, escalation chain
- **Workflow** — matter workspaces, portfolio log, OC status cadence,
legal hold refresh cadence
- **Integrations** — document storage / e-filing / calendar / Slack
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:
- *Side mixed → defense-only:* "`/matter-intake` will stop asking the
plaintiff-side questions. `/demand-draft` will still work for
defense-side pre-suit demands but the starting frame will be different."
- *Risk calibration tightening high-risk threshold:* "More inbound
demands and subpoenas will route through `/matter-briefing` and
`/oc-status`."
- *New standing OC for IP matters:* "`/oc-status` will include this firm
in weekly sweeps for IP-tagged matters."
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 `/litigation-legal:customize` anytime.
## Guardrails
- **Never delete a section.** If the user wants to "remove" a matter type
from scope, offer to mark it `[Not currently handled]` and explain what
intake routing changes.
- **Flag internal inconsistency.** If the change would make the profile
inconsistent (e.g., plaintiff-only side + defense-only OC roster; or
"high volume" portfolio + no matter workspaces configured), flag the
tension.
- **Flag guardrail degradation.** The FRE 408 / privilege gate on
`/demand-draft`, the privilege header on matter outputs, source
attribution tags, and `[verify]` tags on cited authorities are load-
bearing — do not remove. The `[review]` flag and the "do not file
without attorney review" framing are load-bearing.
- **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 Agent setup: memory, context, orchestration →customize by other authors comes first.