A plugin turns scattered agent configuration into a versioned package. It bundles skills with slash commands, isolated subagents, MCP server configurations, and lifecycle hooks, then distributes them as one installable unit. section 3.3.6
The convenience creates supply-chain risk. A plugin can install executable scripts and configuration from the internet, so teams should allowlist marketplace sources, inspect behavior, and govern plugins like production dependencies. section 3.3.6
A disciplined plugin workflow makes team context transferable:
- Encode approved conventions, review checklists, deployment procedures, and MCP connections as reusable components. section 3.3.6
- Version and install the combination as one artifact rather than rebuilding each developer's setup manually. section 3.3.6
- Review the package contents before adoption, treating its marketplace or private registry as a dependency channel rather than a trust signal. section 3.3.6
pull-request-review/ ├── SKILL.md # frontmatter + instructions ├── references/ # the full review checklist ├── scripts/ # run-lint.sh, check-migrations.sh └── assets/ # PR description template
Shows how a bundled skill can organize instructions, references, scripts, and workflow assets inside a distributable package. section 3.3.6








