plugins
4 questions
- AI
How do I make my plugin depend on another plugin without breaking when they ship a release?
Declare plugin dependencies with semver ranges in plugin.json, tag releases with the required convention, and configure cross-marketplace trust carefully. The npm source caveat and three error codes are the most common trip points.
- AI
How do I run a plugin marketplace for my team or community?
A marketplace is a `.claude-plugin/marketplace.json` catalog hosted in a git repo. You list plugins by name and source (relative path, github, git URL, git-subdir, or npm), users add the marketplace once with `/plugin marketplace add owner/repo`, and updates land via `/plugin marketplace update`. The hard parts are versioning discipline, gating for private repos, and using `strictKnownMarketplaces` in managed settings to lock down what users can install.
- AI
How do I share my Claude Code setup as a plugin with one config file?
Plugins are how you turn `.claude/` into something a teammate installs with one slash command. Two config files (`plugin.json` + `marketplace.json`), one git repo, one `/plugin install`. Plus the namespacing rule that surprises people and the version-pinning trap that quietly stops updates.
- AI
Should this be a skill, a plugin, a subagent, or an MCP server?
Skills are reusable prompts. Subagents are isolated research workers. MCP servers are persistent stateful tools. Plugins bundle the three for distribution. Pick by asking which property you actually need: persistence, isolation, or reusability.