Two catalogs of "plugin" -- kept deliberately separate.
This site tracks two genuinely different things that both use the word "plugin," and it never lets them blur together:
1. This repo's own 5 real Cowork plugins -- cwc-design, cwc-data, cwc-deploy, cwc-analytics-engineering, cwc-product-management -- each a real directory under plugins/ with a .claude-plugin/plugin.json, one skill, one command, one agent, and a gates.toml declaring which of its actions need operator approval. Catalog: /plugins.
2. Anthropic's own public "cowork-plugin-management" plugin -- described as a tool to "Create new plugins or customize existing ones for your organization's specific tools and workflows," shipping two sub-tools: cowork-plugin-customizer and create-cowork-plugin. This repo's 5 plugins above were not built using this tool -- it's cataloged here for reference and grounding only. Catalog: /external-tools.
repo_plugins and external_plugin_tools are two different D1 tables with different schemas -- structurally impossible to conflate a query across them by accident.
Every repo_plugins row's source_doc is a real plugin.json read this session; gate_status is read from that same plugin's real gates.toml.
The homepage says outright which tool built which plugin, rather than letting "plugin" do double duty silently.
Start here
This repo's 5 plugins → or Anthropic's cowork-plugin-management →