{"version":"2.1.299","anchor":"skill-tool-accepts-unprefixed-skill-names","canonical_anchor":"skill-tool-accepts-unprefixed-skill-names","heading":"Skills can now be run without their plugin prefix","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/skill-tool-accepts-unprefixed-skill-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Skills can now be run without their plugin prefix\n\nIf Claude names a skill without its plugin prefix and exactly one enabled skill matches, the Skill tool now runs that skill instead of failing\n\n**What**\n\nSkills are packaged instructions Claude can run through the Skill tool. Skills that come from a plugin (an add-on package) have the plugin's name in front of their own name. When the name Claude asks for is not found, the Skill tool now compares it with the enabled skills without their prefixes. If exactly one eligible skill matches, it runs that skill.\n\nBefore, the tool replied \"Unknown skill\" and only suggested names that might have been meant.\n\n**Why**\n\nFewer skill runs fail just because Claude dropped the plugin's name from the front of a skill name.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}