Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Skill override "off" in settings.json does not prevent skill from being available/invocable [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#54996•Fetched 2026-05-01 05:48:58
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
dkouldkoul
Participants
dkouldkoulgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Setting a skill to "off" in skillOverrides within ~/.claude/settings.json does not disable the skill. The skill still appears in the available skills list in system-reminder and can be invoked via /skill-name.

What Should Happen?

Skill should not appear in the available skills list in system-reminder

  • Invoking /skill-name should fail or indicate the skill is disabled

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Add a skill override to ~/.claude/settings.json: {
    "skillOverrides": {
    "skill-name": "off" }
    }
  2. Start a new Claude Code session
  3. Observe that skill-name still appears in the available skills list
  4. Type /skill-name— the skill executes instead of being blocked

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

v2.1.123

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can likely be resolved by modifying the skillOverrides configuration in ~/.claude/settings.json to correctly disable the skill.

Guidance

  • Verify that the skillOverrides configuration is correctly formatted and that the skill name matches the one being disabled.
  • Check if there are any other configurations or settings that may be overriding the skillOverrides setting.
  • Try setting the skill to a different value, such as "disabled" or "false", to see if that resolves the issue.
  • Investigate if there are any known issues or limitations with the Opus Claude Model that may be contributing to this behavior.

Example

No code snippet is provided as the issue is related to configuration and not code.

Notes

The issue may be specific to the Opus Claude Model or the v2.1.123 version of Claude Code, and further investigation may be needed to determine the root cause.

Recommendation

Apply workaround: Try modifying the skillOverrides configuration to use a different value, such as "disabled" or "false", to see if that resolves the issue. This is recommended as it is a non-invasive change that can help determine if the issue is related to the configuration.

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…
#api#batch processing#GPU compatibility#latency issue#model 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

claude-code - 💡(How to fix) Fix [BUG] Skill override "off" in settings.json does not prevent skill from being available/invocable [1 comments, 2 participants]