> Disable a community skill installed through the hub without removing its files. Use when the user wants to temporarily quiet a community skill ("disable [skill]"), stop its hooks from firing while keeping its config, or re-enable a previously disabled skill.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add anthropics/claude-for-legal --skill "disable" -g -a claude-code -yOr manually — copy the SKILL.md below into:
~/.claude/skills/disable/SKILL.md---
name: disable
description: >
Disable a community skill installed through the hub without removing its
files. Use when the user wants to temporarily quiet a community skill
("disable [skill]"), stop its hooks from firing while keeping its config,
or re-enable a previously disabled skill.
argument-hint: "[skill name]"
---
# /disable
Run the `disable` workflow from the skill-manager reference skill against the
named skill.
What disable does:
- Renames the skill's `SKILL.md` to `SKILL.md.disabled` so Claude no longer
discovers it as an active skill. Files, references, templates, and config
stay in place.
- If the skill ships hooks in `hooks/hooks.json`, also rename that file to
`hooks.json.disabled` so no automatic triggers fire while the skill is
disabled.
- Logs the action to
`~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml`.
Safety rules:
1. **Only disable community skills installed through this hub.** Same check
as uninstall — consult the install log and CLAUDE.md installed table.
2. **Never disable a first-party plugin's skill.** Off-limits.
3. **Confirm before renaming.** Show the paths, get explicit `yes`.
Re-enable by running the command again with the same skill name — the
skill-manager workflow recognizes a disabled skill and flips the rename back.
> Detailed uninstall, disable, and re-enable workflows live in the
> `skill-manager` reference skill — load it before doing substantive work.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session