skill-manager

Original：🇺🇸 English

Translated

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.

1installs

Sourceanthropics/claude-for-legal

Added on2026-08-27

NPX Install

npx skill4agent add anthropics/claude-for-legal skill-manager

SKILL.md Content

View Translation Comparison →

Skill Manager

Purpose

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.

What this skill may act on

Only community skills installed through this hub. Identification rule:

The skill's name must appear in

~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml

with a most-recent action of

install

or

enable

(not

uninstall

).

The skill's files must resolve to a path outside the built-in plugin directories that ship with claude-for-legal.

If either check fails, refuse and tell the user why. Never delete or rename files inside a first-party plugin.

Built-in plugins (do not touch)

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.

Workflow — uninstall

Step 1: Verify the skill is community-installed

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.

Step 2: Resolve files

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).

Step 3: Show and confirm

Display:

The skill's install directory path
Every file that will be deleted
Any config directories that will NOT be deleted (with a note that the user can delete them manually if desired)

Prompt: "Delete these files? (yes / no)". No deletion without explicit

yes

.

Step 4: Delete

Remove the skill directory.

Step 5: Log and update CLAUDE.md

Append to

install-log.yaml

:

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.

Workflow — disable

Step 1: Verify (same as uninstall Step 1)

Step 2: Identify files to rename

```
SKILL.md
```
→
```
SKILL.md.disabled
```

hooks/hooks.json

→

hooks/hooks.json.disabled

(if present)

Any agent files the skill installs should also have their frontmatter file renamed (e.g.,
```
agents/*.md
```
→
```
agents/*.md.disabled
```
) so scheduled agents stop firing.

Step 3: Confirm

Show the rename list. Prompt: "Disable this skill? (yes / no)".

Step 4: Rename

Perform the renames.

Step 5: Log