{"version":"2.1.277","anchor":"commandskill-schema-gets-a-builtin-marker-to-resolve-name-c","canonical_anchor":"reload-skills-ipc-response-now-marks-bundledbuiltin-skills","heading":"Skills and commands are now marked as builtin to resolve name collisions","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/commandskill-schema-gets-a-builtin-marker-to-resolve-name-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Skills and commands are now marked as builtin to resolve name collisions\n\nClaude Code's own bundled skills and commands are now flagged so name clashes with user or plugin ones resolve predictably\n\n**What**\n\n- The `reload_skills` response the CLI sends now includes a `builtin: true` field on each skill entry whose resolved name matches one of Claude Code's own bundled skills.\n\n- The schema describing an available skill or command gained an optional `builtin` boolean, true only for Claude Code's own built-in commands, used to decide which command a bare `\/name` invocation runs when a user, project, plugin, and MCP command all share the same name.\n\n**Why**\n\nThis removes ambiguity when a skill or command name collides with one of Claude Code's own: it's now possible to tell that a `\/name` invocation is running the built-in version rather than a same-named user, project, plugin, or MCP one.\n\n- Area: Slash Commands\n- Names: `builtin`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}