Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

Skill override resolution now distinguishes synced vs. locally-overridden skills

Turning a skill on/off now correctly distinguishes synced skills from local ones with the same name

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSkillswhat it touches
KindInternal Changesin v2.1.269,
Under the hood

Turning a skill on/off now correctly distinguishes synced skills from local ones with the same name

What

When Claude Code resolves whether a skill has been turned on or off, it now checks whether the skill came from syncedSkills (skills synced from elsewhere). For synced skills, it first checks for a matching local override by the skill's bare name before falling back to a per-source key. New helpers compute a skill's "unqualified name" for this lookup, handle cases where a synced skill's bare name is "reserved" (and thus excluded from override matching), and pick the highest-priority override across project, user, and plugin sources.

Why

This prevents a mistake where toggling a synced skill on or off could accidentally also affect a different, unrelated local skill that happens to share the same bare name.

See this entry in the whole of v2.1.269 →