customize · anthropics/claude-for-legal, privacy-legal — Claude Code skill for profile updates
customize — a skill for Claude Code edits a single setting in a privacy practice profile. It responds to requests to update the profile, a playbook, or a specific section.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install privacy-legal@claude-for-legalWhat customize does
The skill changes one part of a privacy practice profile without repeating the initial interview or editing YAML by hand. It shows the current value, collects a replacement, explains related effects, then writes the confirmed change to the configuration.
Settings include risk posture, escalation contacts, DPA positions, PIA style, DSAR workflow, and matter workspace paths. Company details live in company-profile.md and are shared by all 12 plugins. The skill handles one change at a time and does not delete profile sections.
A profile must already exist. If its configuration is missing or still has [PLACEHOLDER] values, the skill directs the user to run /privacy-legal:cold-start-interview first. It flags conflicting settings and refuses DSAR timelines below the regulatory minimum.
What it helps with
- change risk posture without repeating the interview
- revise escalation contacts or DPA positions
- adjust PIA style and the DSAR workflow
- update matter workspace paths
Example prompts for the agent
- Change the risk posture to conservative.
- Update the escalation contact in my profile.
- Revise the DPA position on data deletion.
How to install customize
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install privacy-legal@claude-for-legalThis installs the whole privacy-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 privacy-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 privacy-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 privacy-legal@claude-for-legal.
What does customize do?
It guides edits to individual parts of a privacy practice profile and saves confirmed changes to the configuration. It flags conflicting settings and does not delete profile sections.
What does customize need to run?
The profile must be set up first. If its configuration is missing or contains [PLACEHOLDER] values, run /privacy-legal:cold-start-interview before using the skill.
Source text
SKILL.md · Apache-2.0
---
name: customize
description: >
Guided customization of your privacy practice profile — change one thing
without re-running the whole cold-start interview. Adjust risk posture,
escalation contacts, DPA playbook, privacy policy commitments, PIA house
style, DSAR process, or matter workspace paths. Use when the user says
"change my [thing]", "update my profile", "edit my playbook", or
"customize".
argument-hint: "[section name, or describe what you want to change]"
---
# /customize
## When this runs
The user typed `/privacy-legal:customize`. They want to change something in
their privacy profile — a risk posture, an escalation contact, a DPA
position, a PIA section, a DSAR timeline — 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/privacy-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 `/privacy-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, jurisdictions, stage, practice
setting, controller vs. processor orientation *(shared across all 12
plugins — changes flow through `company-profile.md`)*
- **Risk posture** — conservative / middle / aggressive, what each means
for processor obligations, cross-border transfers, and retention
- **People** — DPO, privacy team, engineering liaison, outside counsel,
escalation chain
- **DPA playbook** — positions on sub-processor notice, deletion, audit,
liability, international transfers, SCCs — as processor and as
controller
- **Privacy policy commitments** — the commitments your privacy notice
has made that `/policy-monitor` watches practice against
- **PIA house style** — section order, risk scoring, stakeholder framing,
when DPIA triggers apply
- **DSAR process** — verification, statutory timelines per regime,
exemption application, template response structure
- **Workflow** — intake path, matter workspaces, policy-monitor sweep
cadence
- **Integrations** — document storage / privacy tool / Slack 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:
- *Sub-processor notice 30 days → 14 days:* "`/dpa-review` will now flag
anything shorter than 14 days as a deviation. Existing DPAs stay as
logged."
- *New DSAR exemption in the playbook:* "`/dsar-response` will surface this
exemption in the assessment step where the facts match."
- *Risk posture middle → conservative:* "I'll flag more activities for
PIA escalation, recommend stricter SCC clauses, and be more
conservative on retention."
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 `/privacy-legal:customize` anytime.
## Guardrails
- **Never delete a section.** If the user wants to "remove" a regime from
scope, offer to mark it `[Not currently in scope]` and explain what
flagging drops.
- **Flag internal inconsistency.** If the change would make the profile
inconsistent (e.g., "processor only" + controller playbook positions
active; or "no EU nexus" + SCCs in the default template), flag the
tension.
- **Flag guardrail degradation.** The `[review]` flag, source attribution
tags, `[verify]` tags on cited regulations, and the DPIA-trigger
mandatory-check on `/use-case-triage` are load-bearing — do not remove. If
statutory DSAR timelines are adjusted below the regulatory minimum,
refuse and explain why.
- **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 Finance and business →customize by other authors comes first.