disable

Rename SKILL.md and hooks file to disable a community skill.

9.1k|1.8k|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/anthropics/claude-for-legal --skill disable-anthropics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disable
Source: https://github.com/anthropics/claude-for-legal/tree/main/legal-builder-hub/skills/disable
Command: npx skills add https://github.com/anthropics/claude-for-legal --skill disable-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disable a community skill so it stops running its hooks and is no longer discovered by Claude, without removing any of its existing files or configuration.

Core Features & Use Cases

  • Temporarily stop hooks: If the skill includes hooks/hooks.json, it renames that file so automatic triggers do not fire.
  • Keep configuration intact: Renames the skill’s SKILL.md to SKILL.md.disabled so the skill is not discovered, while references, templates, and config remain in place.
  • Audit the change: Records the disable action in ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml.
  • Safety controls: Ensures only community skills installed through the hub are disabled, prevents disabling first-party plugins, and confirms with an explicit yes before renaming paths.

Quick Start

Run: disable [skill name].

Frequently Asked Questions about disable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I temporarily disable a community skill without deleting its files?

To temporarily disable a community skill without deleting it, the tool renames the skill's SKILL.md to SKILL.md.disabled so Claude stops discovering it. This prevents the skill from running while keeping all your existing templates, references, and configuration completely intact.

How do I stop automated hook triggers for a skill I am not using right now?

To stop automated hook triggers, the tool renames the skill's hooks/hooks.json file. This action pauses automatic triggers so they do not fire, while allowing you to easily re-enable the same skill later without needing to reinstall it.

Can I disable built-in first-party plugins with this workflow disablement process?

No, you cannot disable first-party plugins with this workflow disablement process. The tool enforces strict safety controls that prevent disabling first-party plugins, restricting the action to only community skills installed through the legal-builder hub.

Does disabling a skill permanently remove its configuration from my system?

No, disabling a skill does not permanently remove its configuration. The process simply renames the root SKILL.md and optionally the hooks file to stop discovery and triggers, keeping all references, templates, and configuration safely in place for later re-enablement.

Where are skill disablement actions logged for audit and configuration safety purposes?

Skill disablement actions are logged for audit and configuration safety purposes in the install log located at ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml. This records the specific action to maintain a clear history of your workflow changes.

What is the best way to pause a community skill if I need to confirm the action first?

The best way to pause a community skill with confirmation is to run the disable command, which enforces safety checks by requiring an explicit yes before renaming paths. This ensures you do not accidentally quiet a skill during active workflow configuration.