{"version":"2.1.277","anchor":"skill-directory-discovery-gains-a-pre-scan-hook","canonical_anchor":"skill-directory-discovery-gains-a-pre-scan-hook","heading":"Skill directory discovery gains a pre-scan hook","tier":"internal","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/skill-directory-discovery-gains-a-pre-scan-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Skill directory discovery gains a pre-scan hook\n\nSkill discovery now checks for nested project skill directories before loading\n\n**Unclear.** The exact effect of detecting this nested case (for example, skipping or merging) is not stated in the finding.\n\n**What**\n\nBefore Claude Code logs which skill directories it's loading from, it now runs an extra check against the project's skill directories and its \"skills\" configuration setting. This appears to detect whether a project's skills directory is actually located inside another project's already-loaded `.claude` configuration directory.\n\n**Why**\n\nThis likely helps avoid loading the same skills twice or getting confused when one project's skills folder is nested inside another project's configuration directory.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}