{"version":"2.1.283","anchor":"skill-deny-rules-now-also-match-a-skills-new-packaging-ali","canonical_anchor":"skill-deny-rules-now-also-match-a-skills-new-packaging-ali","heading":"Skill deny rules now also match a skill's packaging alias names","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/skill-deny-rules-now-also-match-a-skills-new-packaging-ali","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Skill deny rules now also match a skill's packaging alias names\n\nA permission rule that blocks a skill now also matches the extra names a packaged skill can go by, so it may block skills it used to miss\n\n**Unclear.** It is not clear where the packaging alias names come from or when the extra matching is skipped.\n\n**What**\n\nA skill is a packaged set of instructions Claude can run. Permission rules let you deny it by name. Some skills can be known by more than one name, and Claude Code already checked deny rules against a skill's alias names. It now also checks a second set of names that come from how the skill was packaged.\n\nIf a deny rule matches one of those packaging names, the skill is blocked with \"Skill execution blocked by permission rules\". In some cases this extra matching is skipped.\n\n**Why**\n\nDeny rules now reach more of the names a skill can go by, so a rule that used to let a packaged skill through may now block it. If a skill stops running, check your deny rules.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}