{"version":"2.1.178","anchor":"skill-directory-scoping","canonical_anchor":"skill-directory-scoping","heading":"Skill Directory Scoping","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178\/e\/skill-directory-scoping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.178","markdown":"### Skill Directory Scoping\n\n**What**\n\nSkills can now be scoped to a specific directory subtree. When a scoped and unscoped variant of the same skill exist, the Skill tool picks the most-specific matching directory.\n\n**Details**\n\n- Skill names with a directory scope appear as `apps\/web:deploy` (directory prefix + colon + skill name)\n- The Skill tool prompt now instructs the model: \"When a skill name has both a scoped and an unscoped variant, pick by the files you are working on: if the files are under a variant's directory, invoke that variant (most specific directory wins)\"\n- Marketplace plugin entries can declare specific skill subdirectory paths relative to the plugin root\n\n**Evidence**\n\nSkill tool prompt update (search for `\"Some skills are scoped to a directory\"`, `\"most specific directory wins\"`); plugin schema (search for `\"Path to a skill directory, relative to the plugin root\"`)"}