disable

To temporarily disable a community plugin, the Skill renames the plugin's SKILL.md file to SKILL.md.disabled. This stops the plugin from appearing as active and halts its behavior while preserving all original files and configuration settings for later use.

You can stop hook triggers from firing by disabling the skill that provides them. The Skill locates the hooks/hooks.json file and renames it to hooks.json.disabled, which prevents automatic hook execution while keeping the original hook configuration intact.

Yes, you can re-enable a disabled skill by running the disable command again with the same skill name. This action flips the SKILL.md.disabled and hooks.json.disabled filenames back to their original active states, restoring full skill functionality.

Disabling a skill does not remove its files from your local configuration directory. It only renames the SKILL.md and hooks.json files to a .disabled state, ensuring the skill is quieted but its data remains safely on disk.

The Skill maintains an audit log by writing every disable and re-enable action to the hub install log. This log is stored under your local claude-for-legal configuration directory, providing a record of skill management changes for compliance tracking.

When a skill is disabled, it no longer appears as an active skill during discovery. The renaming of SKILL.md to SKILL.md.disabled effectively hides the skill from the active registry, preventing it from being triggered or loaded by the hub.