Unclear What the check did with such names before this change was not confirmed.
What
claude plugin init creates a new plugin and then checks its own result. That check now treats names it cannot record as a warning.
Why
Creating a plugin whose names the checker cannot record may no longer stop at that final check.
Names in the bundleclaude plugin init
Documented inclaude-code/plugins/cli-reference
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Create a Claude Code plugin touched a line naming claude plugin init after this was published.
`claude plugin init` writes a starter plugin under `~/.claude/skills/`. Scaffold one from your shell:plugins/create see the edit
Confirmed since
Anthropic's documentation has since written up claude plugin init, on Plugin manifest reference.
The error reads `Plugin name "<name>" is reserved: it passes as one of Anthropic's own`, and the warning reads `Plugin name "<name>" reads as one of Anthropic's own`. `claude plugin init` and `claude plugin tag` refuse a name that draws th…plugins/manifest-reference see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the check did with such names before this change was not confirmed.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude plugin init, on Plugin manifest reference.
Anthropic's release notes agree
Fixed installed_plugins.json being rewritten, losing records, when it holds a record this version cannot read; claude plugin commands now…