customize
/customize
Guided customisation of your UK AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customise".
- Author
- uk-agents ↗
- Repository
- uk-legal-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 01.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.06.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Guided customisation of your UK AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customise".
Triggers from the description
Arguments
/customize [section name, or describe what you want to change]
Original author description
Guided customisation of your UK AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customise".
How it works
- When this runs
- What to do
- Guardrails
SKILL.md preview
---
name: customize
description: >
Guided customisation of your UK AI governance practice profile — change one thing
without re-running the whole cold-start interview. Adjust risk posture,
escalation contacts, use-case registry entries, vendor AI positions,
AI policy commitments, impact-assessment house style, or matter workspace
paths. Use when the user says "change my [thing]", "update my profile",
"edit my config", "tune my playbook", or "customise".
argument-hint: "[section name, or describe what you want to change]"
---
# /customize
## When this runs
The user typed `/ai-governance-legal-uk:customize`. They want to change something
in their practice profile — a risk posture, an escalation contact, a playbook
position, a jurisdiction, an output format — without re-running the whole
cold-start interview and without hand-editing YAML.
## What to do
1. **Read the config.** Read
`~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md`
(and `~/.claude/plugins/config/uk-legal-plugins/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 `/ai-governance-legal-uk:cold-start-interview`
> first — customise is for adjusting a profile you already have.
2. **Show the customisable 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 *(shared across all 12 plugins — changes flow through
`company-profile.md`)*
- **Regulatory footprint** — UK GDPR / DPA 2018, ICO AI guidance, CMA, FCA/PRA,
Online Safety Act / Ofcom, MHRA, EU AI Act (if EU nexus), sector regulators
in scope
- **Risk posture** — conservative / middle / aggressive, what each means for
triage and AIA output
- **People** — governance team, AI risk owner, DPO, escalation chain, approvers
- **Use case registry** — approved / conditional / never entries, and
conditions attached to each
- **AI system inventory** — per-system role / tier for EU AI Act (where EU nexus);
UK GDPR Art. 35 DPIA flags; UK regulatory flags. Run `/ai-governance-legal-uk:ai-inventory` for the dedicated editor.
- **Vendor AI governance** — training-on-data, liability, model-change
notice, and other positions in your vendor AI playbook
- **AI policy commitments** — the public or internal commitments your AI
policy has made, that the plugin cross-checks against
- **Impact assessment house style** — AIA section order, risk scoring
format, stakeholder framing
- **Workflow** — intake path, output format, matter workspace paths, review
cadence for the policy monitor
- **Integrations** — what's connected (Slack, document storage,
scheduled-tasks), what falls back
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 of downstream explanation:
- *Risk posture middle → conservative:* "I'll flag more use cases as
conditional rather than approved, surface more AIA follow-ups, and
recommend more conservative vendor AI redlines."
- *Adding an escalation contact:* "Every skill that routes escalations
(`/use-case-triage`, `/vendor-ai-review`, `/reg-gap-analysis`) will now include this
contact on the relevant risk bands."
- *New use case registry entry:* "`/use-case-triage` will match against this entry
on its next run. Existing AIAs aren't rewritten — re-run them if you want
the new posture reflected."
5. **For shared-profile changes** (company name, industry, jurisdictions,
practice setting, stage): write to
`~/.claude/plugins/config/uk-legal-plugins/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 `/ai-governance-legal-uk:customize` anytime.
## Guardrails
- **Never delete a section.** If the user wants to "remove" something, set it
to `[Not configured]` and explain what that means for the plugin's behaviour.
- **Flag internal inconsistency.** If the change would make the profile
inconsistent (e.g., risk posture aggressive + escalation "everything goes to
the GC"; or "EU AI Act in scope" + "no EU nexus established"), flag the
tension and ask which one they want.
- **Flag guardrail degradation.** If the user asks to turn off a guardrail
("stop adding the `[review]` flag," "drop the citations warning," "skip the
privilege header"), explain what the guardrail protects against and confirm
they understand the trade-off. Most guardrails are adjustable — a few are
structural:
- The `[review]` flag mechanism — load-bearing, don't remove.
- Source attribution tags on retrieved content — load-bearing, don't remove.
- `[verify]` tags on cited statutes/regulations — load-bearing, don't remove.
- **One change at a time.** Don't re-ask the whole interview. If the user
wants multiple changes, handle them sequentially and confirm each before
moving on.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · uk-agents/uk-legal-plugins | 100 | Apache-2.0 |
| aipoch/open-science | 100 | Apache-2.0 |
| DingyangLyu/MatClaw | 100 | Apache-2.0 |
| xuzhougeng/wisp-science | 100 | AGPL-3.0 |
| unicomai/wanwu | 100 | Apache-2.0 |
| microsoft/skills | 100 | MIT |
| nanocoai/nanoclaw | 100 | MIT |
| mcarmona1064-cell/clawbridge-ai | 100 | MIT |
| sliamh11/Deus | 100 | MIT |
Database snapshot: 13.11.2026 · package version 4d129c8741c3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95cold-start-interview
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or… - 95cold-start-interview
Run the cold-start interview — learns your AI governance practice and writes `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or… - 100cold-start-interview
Run the cold-start interview — learns your UK AI governance practice and writes `~/.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md` from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing… - 95cold-start-interview
House cold-start for the litigation plugin — branches by role (in-house, firm associate, solo) and side (plaintiff, defense, both), captures risk calibration, landscape, and house style, and writes the practice profile CLAUDE.md. Use on a fresh install, when the user wants to… - 90cold-start-interview
House cold-start for the UK litigation plugin — branches by role (in-house, firm solicitor, barrister, solo) and side (claimant, defendant, both), captures risk calibration, landscape, and house style, and writes the practice profile CLAUDE.md. Use on a fresh install, when the… - 100legal-practice-profile
When setting up the legal pack — captures jurisdiction, role, escalation and playbook into a plain-prose profile every legal skill reads. Triggers on \"set up legal\", \"legal profile\".