{"version":"2.1.283","anchor":"skills-allowed-tools-entries-naming-claude-skill-dir-or-cla","canonical_anchor":"skills-allowed-tools-entries-naming-claude-skill-dir-or-cla","heading":"Skill tool grants with unfillable folder placeholders are now dropped","tier":"notice","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/skills-allowed-tools-entries-naming-claude-skill-dir-or-cla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Skill tool grants with unfillable folder placeholders are now dropped\n\nallowed-tools entries using CLAUDE_SKILL_DIR or CLAUDE_PROJECT_DIR are dropped, with a warning, when there is no folder to fill them in\n\n**Unclear.** How removing the separate naming for synced skills changes what you see is not clear.\n\n**What**\n\nA skill's allowed-tools field can use placeholders that Claude Code fills in with a folder path. What happens when there is no folder to fill in has changed:\n\n- `CLAUDE_SKILL_DIR`: if the skill has no folder of its own, entries that use it are dropped and a warning is logged.\n\n- `CLAUDE_PROJECT_DIR`: if the session has no working directory, entries that use it are dropped.\n\nBefore, such placeholders were left unfilled, or the project one fell back to the current directory. Synced skills also no longer get a separate naming scheme of their own.\n\n**Why**\n\nAn unfilled placeholder inside a permission grant could match something it was never meant to. Dropping the entry closes that gap, though a skill that relied on it will now ask for those tools instead.\n\n- Area: Skills\n- Names: `allowed-tools`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}