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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.0w
- Forks
- 2.0k
01 前言 Front Matter
- name
- disable
- description
- 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.
- argument-hint
- [skill name]
03 SKILL.md 正文
/disable
Run the disable workflow from the skill-manager reference skill against the
named skill.
What disable does:
- Renames the skill's
SKILL.mdtoSKILL.md.disabledso 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 tohooks.json.disabledso 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-managerreference skill — load it before doing substantive work.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.