Verified:GitHub

disable

Name: disable
Availability: InStock
Author: ZekaiSuni

Disable community skills installed via legal-builder-hub by stopping discovery and hooks while preserving files and configuration.

100|16|Updated May 13, 2026

Search Tags:#workflow execution #skill management #hook control #configuration preservation #plugin hub #disable enable

Ready to run

npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill disable-zekaisuni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: disable
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/legal-builder-hub/skills/disable
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill disable-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a community-installed skill starts firing hooks or producing unwanted behavior, you need a safe way to temporarily silence it without deleting its files or losing its configuration.

Core Features & Use Cases

Disable community skills without removing files by renaming the skill's SKILL.md so it is no longer discovered as active.
Stop hook execution by disabling hooks/hooks.json as well, preventing automatic triggers while disabled.
Re-enable the same skill later using the same command, restoring discovery and hook behavior based on the hub workflow.

Quick Start

Run the disable command for the skill you want to silence, for example: disable example-skill.

Frequently Asked Questions about disable

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

FAQPage Schema

How do I disable a community skill without deleting its configuration files?▼

Disabling a community skill without deleting files involves renaming the skill's SKILL.md so it is no longer discovered as active, while preserving all existing files and configuration for later restoration.

How does hook control work when temporarily turning off an installed plugin?▼

Hook control during plugin deactivation works by renaming the optional hooks/hooks.json file, preventing automatic triggers from firing while the community skill remains safely disabled for troubleshooting.

Can I re-enable a disabled skill later using the same workflow management command?▼

Re-enabling a disabled skill uses the same disable command to restore discovery and hook behavior based on the hub workflow, safely reversing the temporary file renames applied during the initial deactivation.

Does the disable command work with first-party skills installed through the plugin hub?▼

The disable command does not work with first-party skills, enforcing a strict off-limits rule that restricts deactivation to only community skills installed through the legal-builder-hub for safe troubleshooting.

Why are disabled skills still showing up in my workflow execution logs?▼

Disabled skills should not trigger in active workflow execution because the deactivation process consults hub install logs and CLAUDE.md for eligibility, logging the disable action to the hub install log path.