Skip to content
Skills Library
Law & compliance · Tool integration

customize

/customize

Guided customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize".

Licence
Apache-2.0
Last repository change
13.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.05.2026, without references to retired models or APIs.

Licence

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 customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize".

Triggers from the description

change my [thing]add a registryupdate my profileedit my configcustomize

Arguments

/customize [section name, or describe what you want to change]
Original author description

Guided customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize".

How it works

  1. When this runs
  2. What to do
  3. Guardrails
Original SKILL.md headings · 85 lines, 542 words
SKILL.md preview
---
name: customize
description: >
  Guided customization of your Legal Builder Hub profile — change one thing
  without re-running the whole cold-start interview. Adjust practice profile,
  installed starter pack, watched registries, update preferences, or QA
  strictness. Use when the user says "change my [thing]", "add a registry",
  "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 `/legal-builder-hub:customize`. They want to change something
in their Builder Hub profile — a watched registry, update notification
preferences, a practice area for recommendations — 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/legal-builder-hub/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 `/legal-builder-hub: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 *(shared across all 12 plugins — changes flow through
     `company-profile.md`)*
   - **Your practice profile** — practice areas in scope, used to recommend
     community skills
   - **Installed starter pack** — which plugins and skills are installed via
     the hub, with install source
   - **Watched registries** — GitHub repositories / URLs the hub pulls
     community skills from
   - **Update preferences** — check cadence (daily / weekly / on demand),
     notification channel (Slack / in-session), auto-update vs. prompt
   - **QA strictness** — how aggressively `/qa` flags issues on a candidate
     skill before install (lenient / middle / strict), and which
     failure-mode checks are on
   - **Skill install defaults** — install scope (user / project), whether
     to run `/qa` automatically before install
   - **Integrations** — 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 a new watched registry:* "`/browse` will search this registry
     alongside the existing ones. `/update` will check it on its next run."
   - *QA strictness strict → middle:* "`/qa` will report the same findings
     but not block install on the medium band unless you confirm."
   - *Auto-update on → off:* "The hub will prompt you before applying
     updates instead of applying them automatically."

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 `/legal-builder-hub:customize` anytime.

## Guardrails

- **Never delete a section.** If the user wants to "remove" a watched
  registry, offer to mark it `[Paused]` and explain that pausing keeps the
  install history but stops update checks.
- **Flag internal inconsistency.** If the change would make the profile
  inconsistent (e.g., auto-update on + QA strictness off; or practice
  profile that doesn't match any installed plugin), flag the tension.
- **Flag guardrail degradation.** The Legal Skill Design Framework checks
  (nine design parameters, three legal failure modes, trust-surface check)
  are what `/qa` exists to run — turning them off defeats the point. If the
  user wants to lower strictness, recommend the middle band rather than
  disabling the check.
- **One change at a time.** Don't re-ask the whole interview.

Versions

RepositoryScoreLicence
This page · zekaisuni/claude-for-legal-turkish100Apache-2.0
aipoch/open-science100Apache-2.0
DingyangLyu/MatClaw100Apache-2.0
xuzhougeng/wisp-science100AGPL-3.0
unicomai/wanwu100Apache-2.0
microsoft/skills100MIT
nanocoai/nanoclaw100MIT
mcarmona1064-cell/clawbridge-ai100MIT
sliamh11/Deus100MIT

Database snapshot: 13.11.2026 · package version f1e7577e4f8b (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

  • 100cold-start-interview
    Practice-profile interview that recommends and installs a starter pack of community legal skills. This IS the cold start for the whole ecosystem — it asks what kind of lawyer you are and recommends what to install first. Use on fresh install, when the user says "get me started"…
  • 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\".
  • 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
    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…
  • 90cold-start-interview
    执行审计冷启动采访,学习事务所的审计方法论并写入 Practice Profile。 在插件首次使用、配置文件缺失或仍包含 [PLACEHOLDER] 标记时使用。 这是唯一能在未配置状态下运行的技能。

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.