{"version":"2.1.292","anchor":"resuming-a-forked-skill-agent-can-be-refused-because-of-an-o","canonical_anchor":"resuming-a-forked-skill-agent-can-be-refused-because-of-an-o","heading":"Some skill agents can no longer be resumed when your organization turns skills off","tier":"notice","area":"Skills","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/resuming-a-forked-skill-agent-can-be-refused-because-of-an-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Some skill agents can no longer be resumed when your organization turns skills off\n\nClaude Code now refuses to resume a skill agent whose skill your organization's Skills setting turns off, not only synced ones\n\n**What**\n\nSome skills run as a separate helper agent. Claude Code checks a skill before it continues an earlier run of one of these agents. That check now covers more skills, including ones hidden by the host's skill catalog. If your organization's Skills setting turns the skill off, Claude Code refuses to resume it and says the skill is one \"which your organization's Skills setting currently turns off; refusing to resume it.\"\n\nBefore, only synced skills with syncing disabled were refused.\n\n**Why**\n\nSkills your organization has turned off stay off, even when a helper agent that used one is resumed.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}