메뉴
Reference: detailed uninstall, disable, and re-enable workflows for community skills installed via the legal builder hub. Safe by default — refuses to touch first-party plugin skills, confirms before removing files, and logs every action. Loaded by the /legal-builder-hub:uninstall and /legal-builder-hub:disable skills.
Cold-start interview — builds your watchlist, indexes the policy library, and learns your materiality threshold so the monitor surfaces signal instead of noise. Use on fresh install, when reconfiguring (--redo), or when re-checking what connectors are actually responding (--check-integrations).
Guided customization of your regulatory practice profile — change one thing without re-running the whole cold-start interview. Adjust watched regulators, policy library index, materiality threshold, gap response process, feed configuration, or matter workspace paths. Use when the user says "change my [thing]", "add a regulator", "update my watchlist", "edit my threshold", or "customize".
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
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 contains `[PLACEHOLDER]` markers, or when user says "set up ai governance plugin", "onboard me", "configure ai governance".
Guided customization of your 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 "customize".
Run the cold-start interview to learn your commercial contracts practice and write your team practice profile. Use on first use of the plugin, when `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md` is missing or still contains template placeholders, or when the user says "set up the plugin", "configure commercial contracts", "onboard me", or "let's get started". This is the only skill that should run on a fresh install.
| name | skill-manager |
| description | Reference: detailed uninstall, disable, and re-enable workflows for community skills installed via the legal builder hub. Safe by default — refuses to touch first-party plugin skills, confirms before removing files, and logs every action. Loaded by the /legal-builder-hub:uninstall and /legal-builder-hub:disable skills. |
| user-invocable | false |
Remove or quiet a community skill after install. Symmetric with the installer:
the installer writes files with user approval, the skill-manager removes or
disables them with user approval. The installer's audit trail (install-log.yaml)
is the source of truth for what this skill may act on.
Only community skills installed through this hub. Identification rule:
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml
with a most-recent action of install or enable (not uninstall).If either check fails, refuse and tell the user why. Never delete or rename files inside a first-party plugin.
The 12 core plugins that ship with claude-for-legal are off-limits from this
command. The canonical list lives in the hub's CLAUDE.md under "Built-in
plugins." Examples include commercial-legal, corporate-legal,
employment-legal, privacy-legal, product-legal, regulatory-legal,
ai-governance-legal, litigation-legal, litigation-legal,
law-student, legal-clinic, and the hub itself (legal-builder-hub). If
the caller names a skill that resolves into any of these, refuse.
Read install-log.yaml. Find the most recent entry for the named skill.
If not found or if the last action is uninstall: say so and stop.
Determine the install path from the log (written at install time).
Enumerate every file and subdirectory. Also identify any config the skill
wrote to the user's ~/.claude/plugins/config/... — surface this to the user
but do not delete it by default (configuration may be worth keeping for a
later re-install).
Display:
Prompt: "Delete these files? (yes / no)". No deletion without explicit yes.
Remove the skill directory.
Append to install-log.yaml:
- skill: <name>
action: uninstall
timestamp: <ISO8601>
path: <deleted path>
Remove the skill's row from the installed starter pack table in the hub's CLAUDE.md.
SKILL.md → SKILL.md.disabledhooks/hooks.json → hooks/hooks.json.disabled (if present)agents/*.md → agents/*.md.disabled) so scheduled
agents stop firing.Show the rename list. Prompt: "Disable this skill? (yes / no)".
Perform the renames.
Append to install-log.yaml with action: disable.
If the user names a skill whose most recent log action is disable, offer
to re-enable: reverse the renames, log action: enable.
yes./plugin for plugin management.~/.claude/plugins/config/claude-for-legal/<plugin>/ are preserved unless
the user asks for them explicitly.