claude-code - 💡(How to fix) Fix Feature request: disabledSkills setting + status bar indicator for per-session skill toggle [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45225Fetched 2026-04-09 08:10:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

Workaround (until native support lands)

I built a hook-based workaround that achieves the same effect:

Code Example

Settings validation failed:
- : Unrecognized field: disabledSkills

---

#!/bin/bash
STATE_FILE="$HOME/.claude/superpowers.state"
state=$(cat "$STATE_FILE" 2>/dev/null || echo "on")

if [ "$state" = "off" ]; then
  printf '{"hookSpecificOutput":{"hookEventName":"UserPromptSubmit","additionalContext":"[SUPERPOWERS DISABLED] Do NOT auto-invoke any superpowers:* skills this session. Only use them if the user explicitly says use superpowers."}}'
fi

---

#!/bin/bash
STATE_FILE="$HOME/.claude/superpowers.state"
current=$(cat "$STATE_FILE" 2>/dev/null || echo "on")

if [ "$current" = "off" ]; then
  echo "on" > "$STATE_FILE"
  echo "Superpowers ENABLED"
else
  echo "off" > "$STATE_FILE"
  echo "Superpowers DISABLED"
fi

---

sp_state=$(cat ~/.claude/superpowers.state 2>/dev/null || echo "on")
if [ "$sp_state" = "off" ]; then
  printf " \033[2;31m[✖️ superpowers]\033[0m"
else
  printf " \033[1;32m[✔️ superpowers]\033[0m"
fi

---

"hooks": {
  "UserPromptSubmit": [
    { "hooks": [{ "type": "command", "command": "/bin/bash ~/.claude/superpowers-hook.sh" }] }
  ]
}
RAW_BUFFERClick to expand / collapse

Problem

Skills like superpowers are powerful but sometimes overkill for casual conversations. Since they auto-trigger based on instructions loaded at session start, there's no way to know if they'll fire or turn them off without digging into settings manually.

Two things are missing:

  1. A disabledSkills setting in settings.json to suppress specific skills globally or by pattern
  2. A visible indicator in the status bar showing whether skills are active

I tried adding "disabledSkills": ["superpowers:*"] to ~/.claude/settings.json but it was rejected:

Settings validation failed:
- : Unrecognized field: disabledSkills

Workaround (until native support lands)

I built a hook-based workaround that achieves the same effect:

~/.claude/superpowers.state — flag file containing on or off

~/.claude/superpowers-hook.shUserPromptSubmit hook that injects context when disabled:

#!/bin/bash
STATE_FILE="$HOME/.claude/superpowers.state"
state=$(cat "$STATE_FILE" 2>/dev/null || echo "on")

if [ "$state" = "off" ]; then
  printf '{"hookSpecificOutput":{"hookEventName":"UserPromptSubmit","additionalContext":"[SUPERPOWERS DISABLED] Do NOT auto-invoke any superpowers:* skills this session. Only use them if the user explicitly says use superpowers."}}'
fi

~/.claude/toggle-superpowers.sh — toggle script run via ! ~/.claude/toggle-superpowers.sh:

#!/bin/bash
STATE_FILE="$HOME/.claude/superpowers.state"
current=$(cat "$STATE_FILE" 2>/dev/null || echo "on")

if [ "$current" = "off" ]; then
  echo "on" > "$STATE_FILE"
  echo "Superpowers ENABLED"
else
  echo "off" > "$STATE_FILE"
  echo "Superpowers DISABLED"
fi

Status bar indicator added to custom statusline script:

sp_state=$(cat ~/.claude/superpowers.state 2>/dev/null || echo "on")
if [ "$sp_state" = "off" ]; then
  printf " \033[2;31m[✖️ superpowers]\033[0m"
else
  printf " \033[1;32m[✔️ superpowers]\033[0m"
fi

Registered in settings.json:

"hooks": {
  "UserPromptSubmit": [
    { "hooks": [{ "type": "command", "command": "/bin/bash ~/.claude/superpowers-hook.sh" }] }
  ]
}

Requested native solution

  1. disabledSkills array in settings.json supporting exact names and wildcards (e.g. "superpowers:*")
  2. Built-in status bar token showing active/disabled skill groups — so users can glance at the status bar each session and know what's armed
  3. Optionally: a /skills toggle command for per-session override without editing files

extent analysis

TL;DR

To address the issue of lacking control over skills like superpowers, utilize the provided workaround by implementing a hook-based solution that includes a flag file, a hook script, and a toggle script.

Guidance

  • Implement the ~/.claude/superpowers.state flag file to store the state of superpowers as either "on" or "off".
  • Use the ~/.claude/superpowers-hook.sh script as a UserPromptSubmit hook to inject context when superpowers are disabled.
  • Register the hook in settings.json under the "hooks" section for the UserPromptSubmit event.
  • Add a status bar indicator using the custom statusline script to visually represent the state of superpowers.

Example

The superpowers-hook.sh script can be used as follows:

#!/bin/bash
STATE_FILE="$HOME/.claude/superpowers.state"
state=$(cat "$STATE_FILE" 2>/dev/null || echo "on")

if [ "$state" = "off" ]; then
  printf '{"hookSpecificOutput":{"hookEventName":"UserPromptSubmit","additionalContext":"[SUPERPOWERS DISABLED] Do NOT auto-invoke any superpowers:* skills this session. Only use them if the user explicitly says use superpowers."}}'
fi

Notes

This workaround provides a temporary solution until native support for disabling skills and displaying their status in the status bar is implemented.

Recommendation

Apply the workaround by implementing the hook-based solution, as native support for the requested features is not currently available. This approach allows for control over skills like superpowers and provides a visible indicator of their status.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING