customize · anthropics/claude-for-legal, regulatory-legal — Claude Code skill: profile setup
The customize Claude Code skill edits individual settings in a regulatory practice profile. It runs when someone asks to change watched regulators, a threshold, or another profile section.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install regulatory-legal@claude-for-legalWhat customize does
The skill updates one part of a regulatory practice profile without repeating the setup interview. It displays the current settings, gathers a replacement value, explains downstream effects, then writes the confirmed edit to the configuration.
It can adjust watched regulators, the policy library, materiality threshold, gap response process, feeds, and matter workspace paths. Shared company details such as jurisdictions go into company-profile.md and affect the other 12 plugins. A configured profile is required; if its config is missing or contains [PLACEHOLDER], the skill directs the user to run /regulatory-legal:cold-start-interview first.
It keeps profile sections and preserves [verify] and [review] markers. Each run handles one change.
What it helps with
- add a regulator to the watchlist
- change the materiality threshold for digests
- include a policy in the library index
- revise the process for triaging regulatory gaps
Example prompts for the agent
- Add a regulator to the watchlist.
- Change the materiality threshold for the digest.
- Update the matter workspace path.
How to install customize
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install regulatory-legal@claude-for-legalThis installs the whole regulatory-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 regulatory-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 regulatory-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 regulatory-legal@claude-for-legal.
What does customize do?
It edits a selected part of a regulatory practice profile and saves the confirmed change. It flags inconsistencies and keeps profile sections intact.
What does customize need to work?
Set up a profile first by running /regulatory-legal:cold-start-interview. The skill stops if its configuration is missing or still has [PLACEHOLDER] values.
Source text
SKILL.md · Apache-2.0
---
name: customize
description: >
Guided customization of your regulatory practice profile — change one thing
without re-running the whole cold-start interview. Adjust watched
regulators, policy library index, materiality threshold, gap response
process, feed configuration, or matter workspace paths. Use when the user
says "change my [thing]", "add a regulator", "update my watchlist", "edit
my threshold", or "customize".
argument-hint: "[section name, or describe what you want to change]"
---
# /customize
## When this runs
The user typed `/regulatory-legal:customize`. They want to change something
in their regulatory profile — a watched regulator, a materiality threshold,
a feed source — 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/regulatory-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 `/regulatory-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`)*
- **Regulators we watch** — agencies / bodies / SROs / state regulators
in scope, and which are "leading" (most likely to drive policy
impact) vs. "monitor"
- **Policy library** — the internal policies the library indexes, path
to each, owner per policy
- **Materiality threshold** — when a regulatory change rises to
"notable" vs. "report" vs. "digest only"; how this threshold filters
`/reg-feed-watcher` output
- **Gap response process** — who triages, SLA per severity, downstream
owners (policy, product, training)
- **Feed configuration** — regulator feeds, paid feed
connectors, cadence of the `/reg-feed-watcher` sweep, digest channel
- **People** — regulatory counsel, policy owners, comment drafter,
escalation chain
- **Workflow** — matter workspaces, open gaps tracker, comment deadline
tracker, digest publication cadence
- **Integrations** — regulatory feeds / 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 regulator to the watchlist:* "`/reg-feed-watcher` will sweep this
regulator on its next run. `/policy-diff` will accept inputs from this
regulator's rulemaking feed."
- *Tightening materiality threshold:* "`/reg-feed-watcher` digest will be
shorter — items below the new threshold will drop from the weekly
digest but stay searchable."
- *New policy added to the library:* "`/policy-diff` will include this policy
when matching new rules against the library. The comment tracker
will tag comments affecting this policy."
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 `/regulatory-legal:customize` anytime.
## Guardrails
- **Never delete a section.** If the user wants to "drop" a regulator,
offer to mark it `[Monitor only]` and explain that monitoring keeps the
feed in the archive but pulls it out of the active digest.
- **Flag internal inconsistency.** If the change would make the profile
inconsistent (e.g., regulator in scope + no jurisdiction in the footprint
that the regulator covers; or "weekly digest" + materiality threshold
that yields fewer than one item a quarter), flag the tension.
- **Flag guardrail degradation.** `[verify]` tags on cited regulations,
source attribution on feed pulls, and the `[review]` flag on gap triage
are load-bearing — do not remove. Materiality threshold can be adjusted,
but lowering it below the point where the digest becomes noise is the
point — warn if that's the direction.
- **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.