Guided customization of your corporate practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, active modules (M&A / Board / Public Company / Entity Management), materiality thresholds, disclosure schedule format, consent precedents, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customize".
67
81%
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
The user typed /corporate-legal:customize. They want to change something
in their practice profile — a risk posture, an escalation contact, a module
toggle, an output format — without re-running the whole cold-start interview
and without hand-editing YAML.
Read the config. Read
~/.claude/plugins/config/claude-for-legal/corporate-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
/corporate-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:
/diligence-issue-extraction
and /material-contract-schedule will now treat $500K as the cutoff.
Existing findings stay as logged; re-run if you want the new threshold
applied retroactively."/ai-tool- handoff will QA a 10% sample rather than every extraction."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
/corporate-legal:customizeanytime.
[Not configured] and explain what that means for the plugin's behavior.[review] flag, source attribution
tags on retrieved documents, and [verify] tags on cited authorities are
load-bearing — explain the trade-off before removing.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.