Plugins — bundle it all together
Marketplace packages that bundle skills, MCP servers, hooks, and configuration so you can install a whole capability set at once.
A plugin is a package from the Claude Code marketplace that bundles skills, MCP servers, hooks, and other configuration together. Instead of setting up each piece individually, a plugin installs a whole set of capabilities at once.
How plugins work
Marketplaces
Plugins live in marketplace repositories - Git repos that act as a registry of available plugins. Once you add a marketplace to your Claude Code configuration, you get access to every plugin it publishes.
Installing a plugin
After a marketplace is configured, installing a plugin is a single step. You don’t need to manually copy skill files, configure MCP servers, set up hooks, or manage permissions - the plugin handles all of that. One install and everything is wired up.
Updates
When a plugin author pushes changes to the marketplace (new skills, bug fixes, updated MCP configurations), those updates are pulled in automatically. You don’t need to reinstall or manually sync - Claude Code picks up the latest version in the background. This means the whole team stays on the same version without any coordination.
What’s inside a plugin?
A plugin can include any combination of:
| Component | What it provides |
|---|---|
| Skills | Custom slash commands and keyword-triggered prompts |
| Agents | Specialized agents for specific tasks (e.g. orchestration, code review) |
| MCP Servers | Connections to external APIs and services |
| Hooks | Automated actions on session or tool events |
| Settings | Preconfigured permissions and preferences |
Example: adesa-workflow
The adesa-workflow plugin in the Wholesale marketplace is a good example of how a plugin bundles multiple components into a cohesive workflow. It provides a full feature development lifecycle - from discovery through implementation to PR creation - all driven by skills.
Skills included
| Skill | Purpose |
|---|---|
/aw | Main entry point - guides you through planning or implementing a feature |
/aw-discover | Research a feature - query code patterns, schemas, and gather requirements |
/aw-breakdown | Decompose a feature into phased stories with implementation specs |
/aw-coordinate | Identify cross-story dependencies, ordering constraints, and integration risks |
/aw-preflight | Validate contracts, wiring, configuration, and repo state before implementation |
/aw-pickup | Pull a story from ADO, load specs, resolve repos, create feature branches |
/aw-execute | Implement per-repo specs with verification and atomic commits |
/aw-review | Multi-perspective code review across all affected repos |
/aw-verify | Validate implementation against ADO acceptance criteria with evidence |
/aw-pr | Create PRs in each affected repo, linked to ADO work items |
/aw-feedback | Pull PR review comments and address them |
/aw-status | Feature progress dashboard from Azure DevOps |
/aw-sync | Push stories and tasks to Azure DevOps as work items |
/aw-handoff | Save session state for resume in a new conversation |
/aw-reflect | Capture lessons learned to improve future planning |
/aw-repos | Set up team repo registry from the central ownership file |
/aw-context | Bootstrap or update repo context for code repos |
/aw-help | Show available commands, flows, and examples |
Other components
Beyond skills, the plugin also bundles:
- MCP Server connecting to Azure DevOps (work items, PRs, repos, pipelines, wikis, test plans, iterations)
- Agents for specialized tasks like code exploration and orchestration
- Hooks for session state management and context compaction resilience
- Preconfigured permissions for all the tools it provides
How the pieces fit together
This plugin demonstrates how skills can chain together into a workflow. You don’t need to memorize these - just say “I want to work on feature X” and the /aw entry point guides you through the right sequence:
Discover -> Breakdown -> Coordinate -> Preflight -> Pickup -> Execute -> Review -> Verify -> PREach skill handles one phase, passes context to the next, and the plugin’s hooks and agents manage state across the whole flow. A new team member just installs the plugin and says what they want to do.
Example: platform
The platform plugin provides infrastructure scaffolding and pipeline automation for the Platform Team. It can scaffold new Azure Container App and Cloudflare Pages CDN repositories, migrate existing App Services to ACA, and run, monitor, and fix ADO pipelines.
For full documentation, see the Platform Plugin page.
Carvana Marketplaces
Plugins are published to marketplace repositories. Carvana maintains two:
| Marketplace | Description |
|---|---|
| Wholesale Claude Marketplace | Plugins built by the Wholesale team |
| Carvana Claude Marketplace | Plugins shared across Carvana teams |