Guided customization of your litigation practice profile — change one thing without re-running the whole cold-start interview. Adjust practice role, side (plaintiff / defense / mixed), risk calibration, landscape, house style, escalation contacts, severity vocabulary, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customize".
66
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./litigation-legal/skills/customize/SKILL.mdThe user typed /litigation-legal:customize. They want to change something
in their litigation profile — a risk calibration, a house style rule, an
escalation contact, a landscape note — without re-running the whole
cold-start interview and without hand-editing YAML.
Read the config. Read
~/.claude/plugins/config/claude-for-legal/litigation-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
/litigation-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-profile.md)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:
/matter-intake will stop asking the
plaintiff-side questions. /demand-draft will still work for
defense-side pre-suit demands but the starting frame will be different."/matter-briefing and
/oc-status."/oc-status will include this firm
in weekly sweeps for IP-tagged matters."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
/litigation-legal:customizeanytime.
[Not currently handled] and explain what
intake routing changes./demand-draft, the privilege header on matter outputs, source
attribution tags, and [verify] tags on cited authorities are load-
bearing — do not remove. The [review] flag and the "do not file
without attorney review" framing are load-bearing.4a6c651
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.