Customize Skill for Claude

/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

• 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.

• 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

• Ask what they want to change.

> What would you like to adjust? Pick a section, or describe the change in

> your own words.

• 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."

• 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].

• 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.