customize · anthropics/claude-for-legal, employment-legal — Claude Code skill: profile edits and installation
customize is a Claude Code skill for editing an employment-law practice profile one section at a time. It runs when someone asks to revise a jurisdiction, a review rule, or another profile setting.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install employment-legal@claude-for-legalWhat customize does
The skill guides a single profile change without repeating the initial interview or editing YAML by hand. It displays the existing setting, asks for a replacement, explains which downstream workflows will change, then writes the confirmed edit to the configuration.
Editable areas include jurisdictions, risk posture, escalation contacts, hiring and termination review rules, investigation preferences, and matter workspace paths. Shared company details go in company-profile.md and affect other plugins. The skill preserves profile sections and flags inconsistent settings.
A configured profile is required. If the plugin configuration is missing or still has [PLACEHOLDER] values, run /employment-legal:cold-start-interview first. Invoke the skill with /employment-legal:customize.
What it helps with
- revise the jurisdictions in a practice profile
- change hiring or termination review rules
- update escalation contacts
- edit matter workspace paths
Example prompts for the agent
- Add Washington to the profile's jurisdiction list.
- Change the termination review rules and explain the downstream effects.
- Update the escalation contact in my practice profile.
How to install customize
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install employment-legal@claude-for-legalThis installs the whole employment-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 employment-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 employment-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 employment-legal@claude-for-legal.
What does customize do?
It guides edits to one part of an employment-law practice profile, such as its jurisdictions, risk posture, or termination review rules. It shows the current value and asks for confirmation before saving the replacement.
What does customize need to run?
The Claude for Legal plugin configuration must contain an existing profile. If the configuration is missing or has [PLACEHOLDER] values, run /employment-legal:cold-start-interview before using this skill.
Source text
SKILL.md · Apache-2.0
---
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".
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
1. **Read the config.** Read
`~/.claude/plugins/config/claude-for-legal/employment-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 `/employment-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, 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
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 Washington to the jurisdictional footprint:* "`/wage-hour-qa`
and `/termination-review` will start applying WA rules. `/handbook-
updates` will prompt for a WA supplement. `/hiring-review` will now
flag non-compete attempts in WA (unenforceable)."
- *Severance framework 2 weeks/year → 4 weeks/year:* "`/termination-
review` will 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."
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 `/employment-legal:customize` anytime.
## 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.
© Anthropic · Apache-2.0 · anthropics/claude-for-legal
Similar skills
All skills for Agent setup: memory, context, orchestration →customize by other authors comes first.