mcpbeat

Disable

anthropics/disable

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

371 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
8996
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/anthropics/claude-for-legal --skill disable

The instruction itself

1 sections, as written by the author

/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:

  • Only disable community skills installed through this hub. Same check

as uninstall — consult the install log and CLAUDE.md installed table.

  • Never disable a first-party plugin's skill. Off-limits.
  • 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.

How to use it

Copy the folder

Take anthropics/disable from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.