skill manager

Engineering Community

Skill notes

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

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,

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@anthropics · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

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

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

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

04
Step 4: Delete

Remove the skill directory.

05
Step 5: Log and update CLAUDE.md

Append to `install-log.yaml`: Remove the skill's row from the installed starter pack table in the hub's CLAUDE.md.

06
Step 1: Verify (same as uninstall Step 1)

Step 1: Verify (same as uninstall Step 1)

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

08
Step 3: Confirm

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

09
Step 4: Rename

Perform the renames.

10
Step 5: Log

Append to `install-log.yaml` with `action: disable`.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.