Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SkillsArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
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.
