Claude Code Plugins: Package a Setup and Ship It to Your Team — Transcript

Full transcript

1. 0:04A setup you trust is worth more when your whole team runs it.
2. 0:07Plugins are how ClogCode packages a setup and moves it between people.
3. 0:11And there are two sides to that, using the plugins, other people publish, and packaging your own once you've built something worth sharing.
4. 0:18A plugin is one installable unit.
5. 0:21Where it lives sets how you install it.
6. 0:23Inside a session, slash plugin install the organization name at the plugin name does the same thing.
7. 0:29For a team, add a private marketplace once with the slash plugin marketplace at your organization slash cloud plugins or whatever you want to call it.
8. 0:37And every install after that resolves through it with centralized discovery, version tracking, and updates.
9. 0:44Now, a plugin runs code on your machine with your privileges, and its hooks fire on every matching tool call.
10. 0:50Install it for the skills, and you also get its pre-tool use and stop hooks whether you read them or not.
11. 0:55A community plugin can ship a stop hook that calls out to a network endpoint, and nothing in your configuration will warn you.
12. 1:01See every hook, agent, and MCP server that it adds.
13. 1:03Install plugins and add marketplaces only from sources that you truly trust.
14. 1:08The in-app submission form posts to the community marketplace after Anthropix automated review.
15. 1:12and the official marketplace is curated on its own track.
16. 1:15Reviewed isn't the same as Trusted, though, so check what it does.
17. 1:20A plugin doesn't overwrite your configuration.
18. 1:22Its components run alongside yours.
19. 1:24So first, hooks stack together.
20. 1:26A plugin's pre-tool use and your own both fire on every tool call, which is the reason you read the details first.
21. 1:31Skills, agents, and commands are namespaced under the plugin name, so they never clash.
22. 1:36A plugin can also ship a settings.json file, but a narrow one.
23. 1:40So Cloud Code honors only the agent and subagent status line keys.
24. 1:44Setting agent promotes one of the plugin's subagents to the main thread with its system prompt, tool, restrictions, and model.
25. 1:50And enabling that plugin changes how Cloud Code behaves by default, which is one of the main reasons to look before you even turn it on.
26. 1:58So once you've built a .claw directory, instead of your team copying and pasting between machines, package it instead.
27. 2:05A plugin bundles all of it as one version installable unit, skills, subagents, hooks, and MCP server configs, plus the longer tail of the language server protocol servers, background monitors, themes, and a settings.json slice.
28. 2:19The manifest lives at .cloud plugin slash plugin.json and holds the name, version, description, and author.
29. 2:25It's optional, but leave it out and Cloud Code discovers components by directory convention.
30. 2:29The directory structure does the rest.
31. 2:31The same .cloud shape that you already use with skills with one folder per skill, agents with one markdown file per subagent, hooks slash hooks.json and .mcp.json, all at the plugin root.
32. 2:42Name is the only required field.
33. 2:43and it namespaces your skills as the company name, skill name.
34. 2:47Version it like any other dependency.
35. 2:54When you use plugins, read before you install.
36. 2:56When you build one, package your dot cloud the moment it works.
37. 2:59One manifest, one install, and the setup you trust reaches your entire team.