Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Settings reference missing `skillOverrides` setting and its `off` / `user-invocable-only` / `name-only` modes [1 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#56494•Fetched 2026-05-06 06:26:33
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×4

Code Example

{
"skillOverrides": {
"deploy": "user-invocable-only",
"legacy-system-context": "off",
"big-reference": "name-only"
}
}
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

settings.json available settings reference for skill visibility and invocation control

Current Documentation

No documentation currently exists for the skillOverrides setting in the settings reference.

The current docs only describe per-skill frontmatter controls:

By default, Claude can invoke any skill that doesn't have disable-model-invocation: true set.

Hide individual skills by adding disable-model-invocation: true to their frontmatter. This removes the skill from Claude's context entirely.

https://code.claude.com/docs/en/skills

The user-invocable field only controls menu visibility, not Skill tool access. Use disable-model-invocation: true to block programmatic invocation.

https://code.claude.com/docs/en/skills

What's Wrong or Missing?

Claude Code v2.1.129 added working skillOverrides behavior with three modes:

A. The setting itself is undocumented

There is no skillOverrides entry in the settings.json reference, so users cannot discover that this setting exists or where it belongs.

B. The supported values and their effects are undocumented

The docs do not explain that:

  • off hides a skill from both the model and the / menu
  • user-invocable-only hides a skill from the model but keeps it user-invocable
  • name-only collapses the description

C. The relationship to existing skill frontmatter is undocumented

The skills page documents disable-model-invocation: true and user-invocable: false, but it does not explain when a user should use skillOverrides instead of changing each skill's frontmatter.

Suggested Improvement

Add a skillOverrides entry to the settings reference with a concrete JSON example and value semantics.

Suggested addition:

{
"skillOverrides": {
"deploy": "user-invocable-only",
"legacy-system-context": "off",
"big-reference": "name-only"
}
}

Document each mode explicitly:

  • off: hide the skill from the model and from /
  • user-invocable-only: hide the skill from the model but keep it available via /
  • name-only: keep the skill visible but collapse its description

Also add one short cross-reference from the skills page explaining that global settings can override discovery/visibility without editing each skill's SKILL.md.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/settingsMissing skillOverrides setting from the settings.json reference
https://code.claude.com/docs/en/skillsDocuments per-skill frontmatter controls, but not the settings-level override behavior

Total scope: 2 pages affected

Observed against changelog entry for v2.1.129.

extent analysis

TL;DR

Add a skillOverrides entry to the settings reference with a concrete JSON example and value semantics to document the available settings for skill visibility and invocation control.

Guidance

  • Add a skillOverrides section to the settings.json reference page, including a JSON example and explanations for each mode (off, user-invocable-only, name-only).
  • Update the skills page to include a cross-reference to the skillOverrides setting, explaining how global settings can override discovery/visibility without editing each skill's SKILL.md.
  • Verify that the added documentation accurately reflects the behavior of the skillOverrides setting in Claude Code v2.1.129.
  • Review the affected pages (https://code.claude.com/docs/en/settings and https://code.claude.com/docs/en/skills) to ensure consistency and completeness of the documentation.

Example

{
  "skillOverrides": {
    "deploy": "user-invocable-only",
    "legacy-system-context": "off",
    "big-reference": "name-only"
  }
}

This example demonstrates how to use the skillOverrides setting to control skill visibility and invocation.

Notes

The suggested improvement should be reviewed to ensure it accurately reflects the behavior of the skillOverrides setting and is consistent with the existing documentation.

Recommendation

Apply the suggested improvement to add documentation for the skillOverrides setting, as it will make the feature easier to understand and use.

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…
#file not found#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING