{"version":"2.1.274","anchor":"plugin-skill-loading-now-passed-the-plugin-name","canonical_anchor":"plugin-skill-loading-now-passed-the-plugin-name","heading":"Plugin skill loading now passed the plugin name","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/plugin-skill-loading-now-passed-the-plugin-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Plugin skill loading now passed the plugin name\n\nPlugin skill loading now also receives the plugin's own name\n\n**Unclear.** What using the plugin name in the skills loader actually changes for the reader is not stated.\n\n**What**\n\nWhen Claude Code lists what a plugin provides - its commands, agents, skills, hooks, and MCP servers - the function that loads the plugin's skills now also receives the plugin's name, in addition to the skill file path(s) it already received.\n\n**Why**\n\nPassing the plugin name alongside its skill paths likely lets the skill loader associate skills with the plugin they came from, though the finding doesn't specify what this enables in practice.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}