{"version":"2.1.296","anchor":"skills-can-register-hooks-and-tool-grants-via-a-new-path-s4","canonical_anchor":"skills-can-register-hooks-and-tool-grants-via-a-new-path-s4","heading":"Skills with hooks or tool grants are set up through a different path","tier":"internal","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/skills-can-register-hooks-and-tool-grants-via-a-new-path-s4","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Skills with hooks or tool grants are set up through a different path\n\nWhen a skill brings hooks or grants tools, Claude Code now bundles them into one scope instead of registering hooks directly for the session\n\n**Unclear.** It is not clear what the new step does with the skill's hooks and tool grants, so the practical effect on skill permissions is unknown.\n\n**What**\n\nA skill is a packaged set of instructions Claude can call on. Some skills come with hooks (commands that run automatically at certain moments) or grant Claude extra tools. When a skill has either, Claude Code now gathers them into a single scope and hands that to a separate step, instead of registering the hooks straight onto the session. In that case the skill's separate list of allowed tools now comes out empty. Hook registration also now records where the hook came from.\n\n**Why**\n\nThis may change how far a skill's permissions and hooks reach once the skill has been used.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}