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 employment practice profile — change one thing without re-running the whole cold-start interview. Adjust jurisdictional footprint, risk posture, escalation contacts, hiring review rules, termination review rules, handbook positions, investigation preferences, or matter workspace paths. Use when the user says \"change my [thing]\", \"add a jurisdiction\", \"update my profile\", \"edit my config\", or \"customize\".\n",
"argument-hint": "[section name, or describe what you want to change]"
}
/customize
When this runs
The user typed /employment-legal:customize. They want to change something
in their practice profile — a jurisdiction, a risk posture, an escalation
contact, a handbook position — 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/employment-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
/employment-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, practice setting, jurisdictions
(shared across all 12 plugins — changes flow through
company-profile.md) - Jurisdictional footprint — states (and countries) where employees work, single-state vs. multi-state, and any upcoming expansion. This drives state-specific supplement logic.
- Risk posture — conservative / middle / aggressive, what each means for flagging termination risk, restrictive covenant enforceability, and leave accommodation
- People — HR partners, people team lead, outside counsel, escalation chain, investigation sponsor
- Hiring review — offer letter template, restrictive covenants posture, background check vendor, standard at-will language
- Termination review — severance framework, release language, final pay timing rules per state, high-risk flags
- Handbook — handbook file path, state supplements approach, review cadence
- Investigation preferences — privileged labeling, interview protocol, audience-specific summary templates
- Workflow — matter workspaces, leave tracker cadence, expansion project paths
- Integrations — HRIS / Slack / document storage status, fallbacks
- Company / who you are — name, industry, practice setting, jurisdictions
(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 Washington to the jurisdictional footprint: "
/wage-hour-qaand/termination-reviewwill start applying WA rules./handbook- updateswill prompt for a WA supplement./hiring-reviewwill now flag non-compete attempts in WA (unenforceable)." - Severance framework 2 weeks/year → 4 weeks/year: "
/termination- reviewwill use the new baseline in severance calculations." - Risk posture middle → conservative: "I'll flag more terminations for escalation, recommend more protective release language, and be stricter on restrictive covenants."
- Adding Washington to the jurisdictional footprint: "
-
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
/employment-legal:customizeanytime.
Guardrails
- Never delete a section. If the user wants to "remove" a jurisdiction,
offer to mark it
[Not currently staffed — retain rules for re-entry]and explain that going to[Not configured]will drop state-specific flagging. - Flag internal inconsistency. If the change would make the profile inconsistent (e.g., CA in the footprint + aggressive non-compete posture; or risk posture aggressive + "every termination goes to outside counsel"), flag the tension.
- Flag guardrail degradation. The pre-flight citation check, source
attribution tags, and
[verify]tags on cited statutes are load-bearing — do not remove. The[review]flag is load-bearing — explain the trade-off before adjusting. - One change at a time. Don't re-ask the whole interview.
Version History
- 5ceb305 Current 2026-07-05 15:34
