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
2. 0:05your whole team runs it. Plugins are how
3. 0:08Cloud Code packages a setup and moves it
4. 0:09between people, and there are two sides
5. 0:12to that. Using the plugins other people
6. 0:14publish and packaging your own once you
7. 0:16build something worth sharing.
8. 0:18A plugin is one installable unit. Where
9. 0:21it lives sets how you install it. Inside
10. 0:23a session, {slash} plugin install the
11. 0:25organization name at the plugin name
12. 0:28does the same thing. For a team, add a
13. 0:30private marketplace once with the
14. 0:32{slash} plugin marketplace add your
15. 0:34organization {slash} cloud plugins, or
16. 0:36whatever you want to call it, and every
17. 0:38install after that resolves through it
18. 0:40with centralized discovery, version
19. 0:42tracking, and updates.
20. 0:44Now, a plugin runs code on your machine
21. 0:46with your privileges, and its hooks fire
22. 0:48on every matching tool call. Install it
23. 0:50for the skills and you also get its
24. 0:52pre-tool use and stop hooks whether you
25. 0:54read them or not. A community plugin can
26. 0:56ship a stop hook that calls out to a
27. 0:58network endpoint, and nothing in your
28. 0:59configuration will warn you. See every
29. 1:01hook, agent, and MCP server that it
30. 1:03adds. Install plugins and add
31. 1:05marketplaces only from sources that you
32. 1:06truly trust. The in-app submission form
33. 1:09posts to the community marketplace after
34. 1:11Anthropic's automated review, and the
35. 1:13official marketplace is curated on its
36. 1:15own track. Reviewed isn't the same as
37. 1:16trusted, though, so check what it does.
38. 1:19A plugin doesn't overwrite your
39. 1:21configuration. Its components run
40. 1:23alongside yours. So, first, hooks stack
41. 1:25together. A plugin's pre-tool use and
42. 1:27your own both fire on every tool call,
43. 1:29which is the reason you read the details
44. 1:31first. Skills, agents, and commands are
45. 1:33name-spaced under the plugin name, so
46. 1:34they never clash.
47. 1:36A plugin can also ship a settings.json
48. 1:38file, but a narrow one. So, Cloud Code
49. 1:40honors only the agent and sub agent
50. 1:42status line keys. Setting agent promotes
51. 1:45one of the plugin's sub agents to the
52. 1:47main thread with its system prompt,
53. 1:48tool, restrictions, and model. And
54. 1:50enabling that plugin changes how Cloud
55. 1:53Code behaves by default, which is one of
56. 1:54the main reasons to look before you even
57. 1:56turn it on.
58. 1:58So, once you've built a dot cloud
59. 2:00directory, instead of your team copying
60. 2:02and pasting between machines, package it
61. 2:04instead. A plugin bundles all of it as
62. 2:06one version installable unit. Skills,
63. 2:08sub agents, hooks, and MCP server
64. 2:10configs, plus the longer tail of the
65. 2:13language server protocol servers,
66. 2:15background monitors, themes, and a
67. 2:16settings.json slice.
68. 2:19The manifest lives at dot cloud
69. 2:20plugin/plugin.json
70. 2:22and holds the name, version,
71. 2:23description, and author. It's optional,
72. 2:25but leave it out and cloud code
73. 2:27discovers components by directory
74. 2:28convention. The directory structure does
75. 2:30the rest. The same dot cloud shape that
76. 2:32you already use with skills with one
77. 2:34folder per skill, agents with one
78. 2:36markdown file per sub agent,
79. 2:37hooks/hooks.json
80. 2:39and .mcp.json all at the plugin root.
81. 2:41Name is the only required field and it
82. 2:44name spaces your skills as the company
83. 2:46name. skill name. Version it like any
84. 2:48other dependency.
85. 2:54When you use plugins, read before you
86. 2:55install. When you build one, package
87. 2:57your dot [music] cloud the moment it
88. 2:59works. One manifest, one install, and
89. 3:01the setup you trust reaches your entire
90. 3:03team.