$ loading_
Temporarily disable or re-enable an installed community skill without deleting files.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "disable" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-builder-hub/skills/disable/SKILL.md 2. Save it as ~/.claude/skills/disable/SKILL.md 3. Reload skills and tell me it's ready
Please disable this community skill: disable legal-drafter. Before making changes, show the paths to be modified and wait for my explicit yes.
It first lists the skill and hooks file paths to be renamed, then disables the skill after confirmation while keeping its files and configuration.
I want to keep this community skill, but stop its hooks from firing automatically. Run disable compliance-checker and verify it was installed through the hub before proceeding.
It verifies the skill is a hub-installed community skill, then disables the skill and turns off its related hooks.
Please re-enable the previously disabled legal-drafter using the same disable command, and show the file paths that will be restored first.
It detects that the skill is currently disabled, restores the relevant filenames, and re-enables the skill and its hooks if present.
Developers or DevOps users can temporarily disable a hub-installed community skill when troubleshooting conflicts or unwanted behavior without deleting its files or configuration. They can restore it later when needed.
When a community skill ships with hooks that should no longer run automatically, this skill can disable them together with the skill. This preserves the installation while preventing automatic triggers.
If a community skill was only disabled temporarily, users can run the same command again to restore it. This fits cases where a skill needs to be quiet for a while and then brought back.
The README describes how the /disable command invokes the skill-manager reference skill to disable or restore a named community skill. It works by renaming SKILL.md, and optionally hooks/hooks.json, so the skill is no longer discovered and its hooks stop firing, while keeping files, templates, and configuration intact. It also notes that only hub-installed community skills may be handled, first-party skills are off-limits, and explicit confirmation is required before renaming.
Run the disable workflow from the skill-manager reference skill against the
named skill.
What disable does:
SKILL.md to SKILL.md.disabled so Claude no longer
discovers it as an active skill. Files, references, templates, and config
stay in place.hooks/hooks.json, also rename that file to
hooks.json.disabled so no automatic triggers fire while the skill is
disabled.~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml.Safety rules:
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-managerreference skill — load it before doing substantive work.
No. It disables a skill by renaming SKILL.md to SKILL.md.disabled; if hooks/hooks.json exists, it also renames that file to hooks.json.disabled. Files, references, templates, and configuration remain in place.
It can only disable community skills installed through this hub, and it must not disable a first-party plugin's skill. The docs say this should be checked against the install log and the installed table in CLAUDE.md.
Run the same command again with the same skill name. The docs say the skill-manager workflow recognizes that the skill is disabled and flips the rename back.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Standardize new matter intake and generate matter files plus a structured log.
Compare proposed handbook edits and identify cross-reference and state supplement impacts.
Review offer letters and restrictive covenants with jurisdiction-specific hiring checks.
Manage matter workspaces to separate, switch, and archive client contexts.
Safely uninstall, disable, and re-enable community skills with audit logging.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Safely review and install community skills with explicit user approval.
Suggests relevant community skills based on your task and recent plugin activity.
Check installed community skills for updates with diffs and explicit approval.
Perform ClawHub moderation actions like bans, role changes, and status checks.