anthropics / claude-plugins-official
✓ Official★ 31,500A skill package that teaches your agent 44 capabilities — every one documented and browsable below, no GitHub required · by anthropic.
Each skill below is one capability this package teaches your agent. Install the whole package, or open a skill to install just that one.
Manage Discord channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed,…
1 file — installable on its own
Manage Discord channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed,…
1 file — installable on its own
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent…
10 files — installable on its own
Comprehensive guide for building autonomous agents in Claude Code plugins with structured frontmatter, system prompts, and triggering conditions. Agents are autonomous subprocesses defined in markdown files with YAML frontmatter; use them for multi-step independent work, not user-initiated commands Required frontmatter fields: name (3–50 lowercase-hyphenated characters), description (with 2–4 concrete triggering examples), model (inherit/sonnet/opus/haiku), and color...
10 files — installable on its own
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build…
8 files — installable on its own
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build…
8 files — installable on its own
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to…
10 files — installable on its own
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to…
10 files — installable on its own
This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP",…
4 files — installable on its own
This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP",…
4 files — installable on its own
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user…
1 file — installable on its own
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user…
1 file — installable on its own
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations,…
7 files — installable on its own
Analyze codebases and recommend tailored Claude Code automations across all extensibility options. Scans project structure, dependencies, and configuration to identify the most valuable automations for hooks, subagents, skills, plugins, and MCP servers Provides 1–2 focused recommendations per category with specific reasoning tied to detected frameworks, libraries, and patterns Read-only analysis; outputs recommendations for users to implement themselves or request Claude to build Covers MCP...
7 files — installable on its own
Audit and improve CLAUDE.md files to optimize Claude Code's project context. Discovers all CLAUDE.md variants (project root, local overrides, package-specific, global defaults) and evaluates each against a quality rubric covering commands, architecture clarity, patterns, conciseness, currency, and actionability Outputs a detailed quality report with file-by-file scores and specific improvement recommendations before making any changes Applies targeted, minimal updates only after user...
5 files — installable on its own
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files,…
5 files — installable on its own
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command…
13 files — installable on its own
Markdown-based slash commands for defining reusable prompts with dynamic arguments, file references, and bash execution. Commands are instructions written for Claude (not users), stored as .md files in .claude/commands/ , ~/.claude/commands/ , or plugin directories YAML frontmatter configures description, allowed tools, model selection, and argument hints; use $ARGUMENTS , $1 , $2 for dynamic substitution and @file-path syntax for file inclusion Bash execution via backticks gathers dynamic...
13 files — installable on its own
Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do…
1 file — installable on its own
Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do…
1 file — installable on its own
An example user-invoked skill that demonstrates frontmatter options and the skills/<name>/SKILL.md layout
1 file — installable on its own
This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns.…
1 file — installable on its own
Distinctive, production-grade frontend interfaces that reject generic AI aesthetics through intentional design direction. Guides developers through design thinking before coding: establish purpose, tone, constraints, and a memorable differentiator to anchor aesthetic choices Emphasizes typography, color theming, motion, spatial composition, and textural details as core levers for visual impact Explicitly warns against overused fonts (Inter, Roboto, Arial), clichéd color schemes (purple...
8 files — installable on its own
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or…
8 files — installable on its own
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks",…
14 files — installable on its own
Event-driven automation for Claude Code plugins using prompt-based and command hooks. Supports 9 hook events (PreToolUse, PostToolUse, Stop, SubagentStop, UserPromptSubmit, SessionStart, SessionEnd, PreCompact, Notification) for validation, policy enforcement, and workflow automation Prompt-based hooks use LLM reasoning for context-aware decisions; command hooks execute bash scripts for deterministic checks Includes matchers for filtering by tool name (exact, regex, wildcard) and parallel...
14 files — installable on its own
End-to-end onboarding for a freshly-plugged-in M5Stack ESP32 device (Cardputer, Cardputer-Adv, Core, CoreS3, Stick) — detect on USB, flash UIFlow 2.0 firmware,…
1 file — installable on its own
End-to-end onboarding for a freshly-plugged-in M5Stack ESP32 device (Cardputer, Cardputer-Adv, Core, CoreS3, Stick) — detect on USB, flash UIFlow 2.0 firmware,…
1 file — installable on its own
Solve competition math problems (IMO, Putnam, USAMO, AIME) with adversarial
20 files — installable on its own
Solve competition math problems (IMO, Putnam, USAMO, AIME) with adversarial
20 files — installable on its own
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol",…
9 files — installable on its own
Integrate external services into Claude Code plugins via Model Context Protocol servers with four connection types. Supports four server types: stdio for local processes, SSE for OAuth-enabled hosted services, HTTP for REST APIs with token auth, and WebSocket for real-time bidirectional communication Configure MCP servers in dedicated .mcp.json file or inline in plugin.json with environment variable expansion and automatic tool discovery Tools are automatically namespaced and prefixed;...
9 files — installable on its own
Creates interactive HTML playgrounds — self-contained single-file explorers that let users configure something visually through controls, see a live preview,…
14 files — installable on its own
Self-contained HTML playgrounds with live preview, interactive controls, and copyable prompt output. Includes five templates for common playground types: design decisions, data exploration, concept mapping, document critique, and code review Every playground features instant live preview, natural-language prompt generation that only mentions non-default choices, and a one-click copy button Built as single HTML files with no external dependencies, dark theme by default, and sensible presets...
14 files — installable on its own
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin…
11 files — installable on its own
Store per-project plugin configuration and state in .claude/plugin-name.local.md files with YAML frontmatter. Settings files use YAML frontmatter for structured configuration and markdown body for additional context or prompts Hooks, commands, and agents can read settings to customize behavior without requiring code changes Includes bash parsing patterns for extracting individual fields (strings, booleans, numerics) and markdown body content Common patterns include toggling hook activation,...
11 files — installable on its own
Standardized directory structure and manifest configuration for Claude Code plugins with automatic component discovery. Conventional layout with auto-discovery: commands, agents, skills, and hooks load automatically from standard directories without explicit registration Manifest-driven configuration in .claude-plugin/plugin.json supporting metadata, custom component paths, and optional MCP server definitions Portable path references using ${CLAUDE_PLUGIN_ROOT} environment variable for all...
9 files — installable on its own
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up…
9 files — installable on its own
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.
6 files — installable on its own
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.
6 files — installable on its own
Create, test, and iteratively improve AI agent skills with structured evaluation and benchmarking. Guides you through the full skill development lifecycle: intent capture, draft writing, test case creation, evaluation, and iteration based on user feedback Runs quantitative benchmarks comparing skill-enabled vs. baseline performance, with timing and token usage analysis across multiple test cases Generates an interactive browser-based review tool for qualitative evaluation — side-by-side...
29 files — installable on its own
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an…
29 files — installable on its own
Guidance for creating effective, discoverable skills for Claude Code plugins with progressive disclosure and strong triggering. Create skills in the plugin's skills/ directory with SKILL.md (required) and optional references/ , examples/ , and scripts/ subdirectories for progressive context loading Write frontmatter descriptions in third person with specific trigger phrases users would say (e.g., "This skill should be used when the user asks to 'create a hook', 'validate tool use'...") Keep...
3 files — installable on its own
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill…
3 files — installable on its own
Claude Code Plugins Directory
A curated directory of high-quality plugins for Claude Code.
⚠️ Important: Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change. See each plugin's homepage for more information.
Structure
/plugins- Internal plugins developed and maintained by Anthropic/external_plugins- Third-party plugins from partners and the community
Installation
Plugins can be installed directly from this marketplace via Claude Code's plugin system.
To install, run /plugin install {plugin-name}@claude-plugins-official
or browse for the plugin in /plugin > Discover
Contributing
Internal Plugins
Internal plugins are developed by Anthropic team members. See /plugins/example-plugin for a reference implementation.
External Plugins
Third-party partners can submit plugins for inclusion in the marketplace. External plugins must meet quality and security standards for approval. To submit a new plugin, use the plugin directory submission form.
Plugin Structure
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # DocumentationPlugin names are immutable
The name field in a marketplace entry is an immutable slug. Once a plugin has been published, its name must not change — users have it installed under that slug, and renaming it breaks their install with a plugin-not-found error.
- To change how a plugin is labeled in the UI, set or update
displayNameinstead. - If a rename is genuinely unavoidable, add an entry to the top-level
renamesmap in.claude-plugin/marketplace.jsonso existing installs auto-migrate:
"renames": {
"old-name": "new-name"
}The Claude Code plugin loader reads this map and transparently rewrites the old slug to the new one on the user's next sync.
Skill-bundle plugins
When a plugin's source repository ships skills (SKILL.md files) without a .claude-plugin/plugin.json manifest, the marketplace entry can declare the skills directly using strict: false and an explicit skills array.
{
"name": "example-bundle",
"description": "Brief description of the bundled skills.",
"author": { "name": "Author Name" },
"category": "development",
"source": {
"source": "git-subdir",
"url": "https://github.com/example-org/sdk.git",
"path": "packages/agent-skills",
"ref": "main",
"sha": "<commit sha>"
},
"strict": false,
"skills": [
"./skill-a",
"./skill-b",
"./skill-c"
],
"homepage": "https://github.com/example-org/sdk"
}Each path in skills is relative to source.path and points at a directory containing a SKILL.md. Paths can reach deeper than a single level — for example, ["./libA/skill-1", "./libB/skill-2"] exposes a curated subset across multiple library subdirectories. Each skill is registered as <plugin-name>:<skill-name> in Claude Code.
For the underlying schema, see Strict mode in the marketplace documentation.
License
Please see each linked plugin for the relevant LICENSE file.
Documentation
For more information on developing Claude Code plugins, see the official documentation.
Install the whole package (44 skills):
npx skills add https://github.com/anthropics/claude-plugins-officialOr install a single skill:
npx skills add https://github.com/anthropics/claude-plugins-official --skill <name>Pick the skill name from the Skills tab — each entry there installs independently.