Repo plugins vs. Anthropic's plugin-management tool
The word "plugin" is used two different ways in this repository's own ecosystem, and this site exists specifically to keep them from blurring together the way a single "plugins" table would.
repo_plugins
The 5 real cwc-* Cowork plugins this repo ships under plugins/ -- each an installable unit with its own .claude-plugin/plugin.json (name, version, description, commands, skills, agents), its own gates.toml approval policy, its own README and LICENSE. These are consumed BY Claude Code/Cowork sessions working in this repo; they are the finished product.
external_plugin_tools
Anthropic's own public "cowork-plugin-management" plugin is not one of this repo's 5 -- it's a different kind of thing: a tool FOR building plugins like the 5 above, not a plugin this repo ships itself. Its two sub-tools, cowork-plugin-customizer (customize an existing plugin) and create-cowork-plugin (create one from scratch), describe a meta-capability this repo has not used to build cwc-design/cwc-data/cwc-deploy/cwc-analytics-engineering/cwc-product-management -- those 5 were hand-authored directly.
Keeping these in separate D1 tables with separate schemas (rather than one plugins table with a kind column) is a deliberate, slightly stronger guarantee: a query against repo_plugins structurally cannot accidentally return an Anthropic tool row, and vice versa.
See also: the 5 real plugins, the 2 external sub-tools.