18. Packaging and Distributing Workflows (Plugins and Marketplaces)
Show notes
In Episode 18 of Beyond Prompting, author Sho Shimoda explores how to bundle your team's custom skills, commands, subagents, hooks, and MCP server configurations into a single, installable unit using Plugins. Rather than manually sharing scattered configuration files with colleagues, Plugins allow teams to package and distribute entire operational capabilities effortlessly. In this episode, we cover:
- The Anatomy of a Plugin: How a plugin is structured as a directory with a .claude-plugin/plugin.json manifest and optional component folders (skills/, commands/, agents/, hooks/, .mcp.json, and workflows/).
- Automatic Namespacing: How plugin components are namespaced upon arrival (e.g., /acme-standards:review), allowing multiple plugins to coexist safely without name collisions.
- Managing the Lifecycle: Using claude plugin commands (install, enable, disable, update, validate) and browsing official marketplaces (claude-plugins-official and claude-community).
- Publishing Internal Marketplaces: How to host a private team marketplace using a Git repository containing a .claude-plugin/marketplace.json index file.
- Plugins in Cowork: Bundling operational skills, connectors, and subagents for non-engineering teams via the Knowledge Work marketplace.
- Security & Privilege Scrutiny: Why plugins must be audited carefully before installation—since their hooks run on your local machine and their MCP servers spawn local host processes with your full privileges.
(Note for listeners: This episode covers Chapter 18 of Sho Shimoda's book RUNNING CLAUDE: The Operator’s Guide to Chat, Cowork and Claude Code, available on Amazon as the successor book to Master Claude: Chat, Cowork and Code).