A Claude Code Plugin is a bundled distribution unit packaging skills, slash commands, hooks, subagents, and MCP server configurations as a single installable extension to 📝Claude Code.
Plugins emerged as Claude Code's answer to skill and hook sharing — a way for the community to publish curated bundles instead of having users assemble individual files in ~/.claude/. A plugin is structurally a directory or repository that mirrors the standard Claude Code customization layout: a skills/ subdirectory for slash commands, hooks/ configurations for event-driven shell scripts, agents/ for subagent definitions, and optional MCP server registrations. The plugin manifest declares what it exposes and any required permissions.
Installation typically routes through a marketplace registry, a direct GitHub clone, or a claude CLI subcommand. Once installed, the plugin's skills, hooks, and agents register into the user's namespace and become callable like any built-in. Major plugin ecosystems include 📝Everything Claude Code (ECC) with 156 skills and 38 agents, Obra Superpowers focused on methodology and workflow enforcement, and gstack organized around a sprint-sequence configuration for solo founders.
The plugin model raises a meaningful trust surface: installing one means executing arbitrary shell commands and granting tool access to code maintained by third parties. The recommended posture is to read hook files before installing, pin to specific commits rather than tracking main, and run security scans against newly added plugins before allowing their hooks to fire.