{"version":"2.1.296","anchor":"skills-sync-hooks-removal-on-sync-off-and-managed-policy-ma","canonical_anchor":"skills-sync-hooks-removal-on-sync-off-and-managed-policy-ma","heading":"Turning off skills sync now clears hooks that synced skills brought in","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/skills-sync-hooks-removal-on-sync-off-and-managed-policy-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Turning off skills sync now clears hooks that synced skills brought in\n\nWhen skills sync is turned off, hooks from synced skills are now removed and Claude Code records that this happened\n\n**What**\n\nSkills are packaged instructions and tools that Claude Code can use, and skills sync keeps them in step across places. Hooks are scripts that run at set points, such as before or after a tool is used. When skills sync is turned off, Claude Code now removes hooks that came from synced skills and records that it did so.\n\nSeparately, the check of which plugin marketplaces your organisation's managed policy allows is now handled by shared code.\n\n**Why**\n\nTurning off sync no longer leaves behind hooks from skills that are no longer being synced.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}