Under the hood
Plugin skill loading now also receives the plugin's own name
What
When 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.
Why
Passing 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What using the plugin name in the skills loader actually changes for the reader is not stated.