What
Skills that came from your claude.ai account are now blocked consistently on every path when skills sync is switched off or denied by policy, instead of being refused in some places and quietly honoured in others. The change closes the case where an agent that had run as a forked skill could be resumed without that skill's permission scoping, which now fails outright rather than resuming in a weaker state.
Details
- Slash-command dispatch drops the match for a synced skill, and "did you mean" suggestions filter those entries out.
- Invoking a blocked skill returns
Unknown skill, and agent skill loading logs a warning naming it as an account-synced skill while skills sync is currently disabled, whether turned off or denied by policy. - Launching or resuming a forked skill, meaning one that ran in its own agent with the skill's permission scoping, throws instead of proceeding.
- A refused resume is counted under the name
forked_skill_resume_sync_vetoed. - The cache of commands discovered in skill directories now carries the sync state in its key, so results found under one setting are not reused after you toggle it.
- Entries are identified as blocked by the fact that they were loaded from synced skills, so locally authored skills of the same name are unaffected.
Evidence
is an account-synced skill and skills sync is currently disabled (turned off or denied by policy), an account-synced skill that is currently disabled (skills sync turned off or denied by policy); refusing to resume it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.