{"version":"2.1.283","anchor":"skill-not-found-message-now-blames-a-plugin-that-failed-to-l","canonical_anchor":"skill-not-found-message-now-blames-a-plugin-that-failed-to-l","heading":"Missing skill now blamed on a plugin that failed to load","tier":"notice","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/skill-not-found-message-now-blames-a-plugin-that-failed-to-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Missing skill now blamed on a plugin that failed to load\n\nWhen a skill cannot be found because its plugin failed to load, Claude is told the plugin could not load, not that the skill is not installed\n\n**Unclear.** A related change to how skill permissions match names for packaged plugins was seen but not worked out.\n\n**What**\n\nSkills are packaged instructions Claude can call on, and plugins can supply them. When a skill cannot be found and some plugins failed to load, Claude is now told that the plugin could not be loaded here, rather than that the skill is not installed. The message also says what kind of failure it was, for example:\n\n- an invalid plugin manifest, the file describing the plugin\n\n- a dependency that is not met\n\n- a path that was not found\n\n**Why**\n\nThis stops Claude from telling you a skill is not installed when the real problem is a plugin that did not load.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}