customize
GitHub用于在不重新运行冷启动访谈的情况下，调整监管实践配置。支持修改监管机构、政策库、重要性阈值等参数，确保变更安全并通知下游工具同步更新。
Trigger Scenarios
Install
npx skills add anthropics/claude-for-legal --skill customize -g -y
SKILL.md
Frontmatter
{
"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\".\n",
"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
-
Read the config. Read
~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md(and~/.claude/plugins/config/claude-for-legal/company-profile.mdone 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-interviewfirst — 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-watcheroutput - 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-watchersweep, 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
- Company / who you are — name, industry, jurisdictions, stage, practice
setting (shared across all 12 plugins — changes flow through
-
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-watcherwill sweep this regulator on its next run./policy-diffwill accept inputs from this regulator's rulemaking feed." - Tightening materiality threshold: "
/reg-feed-watcherdigest will be shorter — items below the new threshold will drop from the weekly digest but stay searchable." - New policy added to the library: "
/policy-diffwill include this policy when matching new rules against the library. The comment tracker will tag comments affecting this policy."
- Adding a regulator to the watchlist: "
-
For shared-profile changes (company name, industry, jurisdictions, practice setting, stage): write to
~/.claude/plugins/config/claude-for-legal/company-profile.mdand 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:customizeanytime.
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.
Version History
- 5ceb305 Current 2026-07-05 15:39
