Claude Code Field Guide
21 / 35

Plugins (New Since the Video)

A single installable bundle of skills, agents, hooks and MCP servers — the packaging layer that didn't exist yet when the video was made.

Updated since the video
Currency check: Entirely new concept. Skills, agents and hooks existed individually in the video; bundling and distributing them as one unit is new.

The video treats skills, hooks and subagents as separate things you set up individually. Plugins are the packaging layer added since: a self-contained directory that can bundle any combination of skills, custom agents, hooks, MCP server configs, and even language-server integrations into one shareable, versioned unit, installed with /plugin install.

Plugins are distributed through marketplaces — Anthropic curates an official one, there's a public community-reviewed one, and organizations can host private ones for internal tooling. This is the mechanism that makes “download someone else's expert setup” (which the video gestures at loosely for skills and subagents) actually practical: one install command instead of manually copying several separate files and folders.

Installing a language-intelligence plugin

Instead of manually wiring up a language server, a developer installs a pre-built code-intelligence plugin for TypeScript, instantly giving Claude Code precise “go to definition” navigation instead of relying on text search — which also reduces token usage from unnecessary file reads.

An internal company plugin

A company packages its house style skill, its deployment hooks, and its internal ticketing MCP connector into one private plugin, so any employee's Claude Code setup is fully configured with a single internal install command rather than a multi-step onboarding doc.