{"version":"2.1.295","anchor":"skills-policy-and-project-dirs-skipped-under-a-new-predicat","canonical_anchor":"skills-policy-and-project-dirs-skipped-under-a-new-predicat","heading":"Project and synced skills are skipped in a certain session mode","tier":"notice","area":"Skills","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/skills-policy-and-project-dirs-skipped-under-a-new-predicat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Project and synced skills are skipped in a certain session mode\n\nIn a certain session mode, Claude Code now skips skills from project folders and synced user skills, and also skips some git and config lookups\n\n**Unclear.** Which session mode causes project and synced skills to be skipped is not settled.\n\n**What**\n\nSkills are reusable instructions Claude Code can load from folders on your machine. In a certain session mode, Claude Code now loads no skills from project folders and skips user skills that were synced from elsewhere. The same mode also changes other places, including finding the top of a git repository and reading configuration files.\n\n`CLAUDE_CODE_DISABLE_POLICY_SKILLS` works as before.\n\n**Why**\n\nIn this mode Claude Code does not look through your project or git repository for skills and settings, which suggests a remote or locked-down kind of session.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}