What
The local skillOverrides setting, which lets you hide or collapse a skill from settings without editing its file, is now built using a storage object with no inherited prototype instead of a plain JavaScript object. This avoids clashes with built-in object properties.
- The settings dialog used for managing skills now checks which skill names would collide with properties that Settings storage can't hold.
- When a skill's name can't be stored or toggled for this reason, a new message now surfaces explaining that Settings can't store an entry with that name.
Why
This prevents a skill whose name happens to match a reserved property name from silently failing to save its override, and tells you clearly when that happens instead of failing silently.
Names in the bundleskillOverrides
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up skillOverrides, on All settings.
| [`skillOverrides`](#skilloverrides) | [Hide or collapse a skill](/docs/en/skills#override-skill-visibility-from-settings) without editing its SKILL.md | Plugins and skills | Any file |settings-reference see the edit
Added since
A small documentation edit on Extend Claude with skills touched a line naming skillOverrides after this was published.
To raise the budget, set the [`skillListingBudgetFraction`](/docs/en/settings-reference#skilllistingbudgetfraction) setting (for example, `0.02` = 2%) or the `SLASH_COMMAND_TOOL_CHAR_BUDGET` environment variable to a fixed character count.…skills see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Extend Claude with skills touched a line naming skillOverrides after this was published.