Jonathon's AI Wiki

Claude Code Plugins and Marketplaces

9 min read

Source: ai-research (web research, 2026-04-11)

Plugins are the package layer for Claude Code — they bundle skills, agents, hooks, MCP servers, or LSP servers into installable units with version tracking and auto-updates. A plugin marketplace provides discovery, and enterprises can run private registries for governance. This is how the Claude Code ecosystem distributes and manages reusable tooling at scale.

What Plugins Are

  • A plugin is a package that can bundle any combination of (see also Cowork Plugins for the business-team plugin ecosystem):
    • Skills (procedural Markdown instructions)
    • Agents (autonomous worker configurations)
    • Hooks (event-driven automation triggers)
    • MCP servers (Model Context Protocol connectors to external systems)
    • LSP servers (Language Server Protocol for IDE-like intelligence)
  • Plugins have version numbers, changelogs, and support auto-updates
  • They are discovered and installed through marketplaces

Official Registry

  • claude-plugins-official registry: 101 plugins as of April 2026
    • 33 Anthropic-built plugins
    • 68 partner plugins from: GitHub, Playwright, Supabase, Figma, Vercel, and others
  • Auto-update is enabled by default for plugins from official Anthropic marketplaces

Installing Plugins

  • Browse the marketplace: /plugin marketplace add [publisher]/[name]
  • Install a plugin: /plugin install [name]
  • Two-step flow: first add from the marketplace, then install locally
  • Plugins configure themselves — MCP servers, skills, and hooks are registered automatically

Creating Your Own Marketplace

  • Define .claude-plugin/marketplace.json in your repository root
  • Host the repository on GitHub or GitLab
  • Other users can add your marketplace as a source: /plugin marketplace add [your-repo-url]
  • Useful for teams that want to share plugins internally without publishing to the official registry

Enterprise and Private Registries

  • Private registries available via LiteLLM AI Gateway for organizational governance
  • Admins control which plugins are available across the org
  • Supports approval workflows, audit trails, and version pinning
  • Available on Team and Enterprise plans

Plugin authoring (Weeks 13–14, 2026)

Two recent capabilities that significantly change what plugins can ship:

userConfig is now public (Week 13, v2.1.83+)

Plugins can declare userConfig in plugin.json to prompt for settings at enable time and store them with keychain-backed secrets (macOS Keychain, Windows Credential Manager, libsecret on Linux). Previously this was internal-only. Now any plugin can ask “what’s your API key?” / “what’s your default org?” on first install instead of forcing users to edit settings JSON.

Pattern: declare schema-validated config fields with secret: true for credentials. Claude Code prompts the user, validates, persists secrets to the OS keychain, and makes the values available to the plugin’s commands / hooks / agents at runtime.

Executables on PATH via bin/ (Week 14, v2.1.91+)

Drop an executable into a bin/ directory at the plugin root. Claude Code adds bin/ to the Bash tool’s PATH while the plugin is enabled. Claude can invoke the binary as a bare command — no absolute path or wrapper script. Closes the long-standing distribution gap where plugins shipped commands/agents/hooks but had to bundle CLI helpers as separate npm packages or rely on system-installed tools.

my-plugin/
├── .claude-plugin/
│   └── plugin.json
└── bin/
    └── my-tool       # invoked as `my-tool` from any Bash call

Combine with userConfig for a complete deliverable: plugin asks for credentials at enable time → binary in bin/ reads them via env / config → commands / hooks call the binary by name.

Plugin authoring (Weeks 16–17, 2026)

Two more capabilities that expand what plugins can ship:

Background watchers via monitors manifest key (Week 16, v2.1.105)

Plugins can now ship background watchers by declaring a top-level monitors key in plugin.json. Watchers auto-arm at session start or when the skill is invoked, running in the background and streaming events into the conversation. Use for: watching log files, polling CI, listening for file system changes — without requiring the user to start a separate /loop.

{
  "monitors": [
    {
      "name": "build-watcher",
      "command": "tail -f dist/build.log",
      "autoStart": true
    }
  ]
}

Plugins can ship custom themes (Week 17, v2.1.118)

Plugins can now include theme files that install into ~/.claude/themes/ when the plugin is enabled. Each theme picks a base preset (dark, light, etc.) and overrides only the color tokens it cares about. Useful for team/brand enforcement: ship one plugin that enforces a consistent color scheme across all developer terminals in an org.

New plugin management commands (Weeks 17–18)

CommandAddedBehavior
claude plugin tagW17 (v2.1.119+)Creates a release git tag for a plugin with version validation. Supports semantic versioning.
claude plugin prunev2.1.121Removes orphaned auto-installed plugin dependencies (packages installed as plugin dependencies but no longer referenced).

Plugin authoring (Week 19, 2026)

Load plugins from .zip archives and URLs (W19, v2.1.128+)

Two new ways to load plugins without installing via a marketplace — useful for testing before publishing, or distributing internal plugins from an artifact store:

  • claude --plugin-dir ./plugin.zip — --plugin-dir now accepts a .zip archive of a plugin directory in addition to a directory path
  • claude --plugin-url https://example.com/my-plugin.zip — new flag that fetches a plugin archive from any URL for the current session
# Load from local zip
claude --plugin-dir ./my-plugin.zip
 
# Load from URL
claude --plugin-url https://artifact-store.example.com/my-plugin.zip

Both approaches are session-scoped — the plugin is active for that session only, not installed permanently. Use claude plugin install for permanent installation.

Community Registries

  • SkillsMP — 800,000+ agent skills searchable in one catalog
  • TokRepo — 500+ skills, MCP servers, and workflows curated for discovery
  • awesome-claude-skills on GitHub — 1,234+ skills with community ratings and reviews
  • Claude Skills Hub (claudeskills.info) — 658+ skills with a unique angle: foregrounds cross-vendor official collections (Anthropic 16, OpenAI 37, Microsoft 333, Google 11, Vercel 8, GitHub Copilot 324, WordPress) alongside curator bundles (Trail of Bits, Cybersecurity Skills 734+ MITRE-mapped, Everything Claude Code 86+, PM Skills 63). Featured on Product Hunt. Discovery surface — install via the underlying GitHub repo of any listed skill.
  • Community registries are not auto-updated; manual review and install is recommended

Canonical Anthropic Skill Repository

  • skills (124k stars) is technically a plugin marketplace too — /plugin marketplace add anthropics/skills registers it, and you install document-skills@anthropic-agent-skills or example-skills@anthropic-agent-skills from there. It’s the canonical reference repo for the Agent Skills standard and contains the formal spec/agent-skills-spec.md, a starter template/, and 17 example skills. Treat it as a sibling marketplace to claude-plugins-official rather than a community registry — Anthropic-run, but separate from the headline registry.

Third-party Frameworks (skills/orchestration on top of Claude Code)

Three large community projects ship as Claude Code distributions and represent distinct shapes of the same problem space — extending Claude Code with structured methodology, command surfaces, or multi-agent orchestration.

  • Superpowers (168k stars, MIT) — Auto-triggering skills bundle from Jesse Vincent / Prime Radiant. Distributed via the official claude-plugins-official marketplace (/plugin install superpowers@claude-plugins-official). Closed methodology, mandatory TDD, seven-phase workflow. Multi-agent across Claude Code, Codex, Cursor, Copilot, Gemini. Pick when you want one disciplined methodology applied uniformly without remembering command names.
  • SuperClaude Framework (22.5k stars, MIT) — Configurable surface area: 30 /sc:* slash commands, 20 agents, 7 behavioral modes, 8 MCP server integrations. Installed via pipx (pipx install superclaude && superclaude install). Not on the official marketplace; v5.0 will move to plugin distribution. Pick when you want à-la-carte commands and behavioral modes.
  • oh-my-claudecode (OMC) (30k stars, MIT) — Orchestration-first plugin + CLI from Yeachan Heo. 6 orchestration modes, ~19 specialized agents, magic keywords, HUD statusline, cross-model advisors (Codex / Gemini). Install via /plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode or npm. Pick when you want explicit multi-agent orchestration patterns.

These three frameworks coexist with native Agent Teams, Subagents, and Managed Agents — the third-party layer doesn’t replace the Anthropic primitives, it composes opinions on top of them.

Notable individual skills (2026-04-27 batch)

Cross-cutting skills installed independently of the larger frameworks/marketplaces above. All MIT, all installable via /plugin marketplace add <owner>/<repo> unless noted.

  • last30days-skill (mvanhorn, 24.2k stars) — Multi-platform research aggregator with v3 pre-research brain. Engagement-ranked output across Reddit / X / YouTube / TikTok / HN / Polymarket / GitHub / web. Multi-runtime: Claude Code, OpenClaw, Claude.ai .skill upload. Depends on yt-dlp for YouTube.
  • social-media-skills (Charlie Hills) (372 stars) — 16-skill voice-first content system for LinkedIn / Reels / YouTube / X / Substack. Sibling to Corey Haines’ Marketing Skills Bundle (breadth vs depth on social/newsletter).
  • birdclaw (steipete, 377 stars) — Local-first X/Twitter workspace + .agents/skills/birdclaw agent skill for AI access to tweets/DMs/likes/bookmarks via stable JSON. SQLite + FTS5 + JSONL Git backups.
  • ai-website-cloner-template (JCodesMore, 12.9k stars) — Next.js 16 reverse-engineering template. /clone-website <url> runs recon → spec → parallel git-worktree builders → QA. Multi-agent (Claude Code + 11 others).
  • yt-dlp (Unlicense) — Not a Claude skill. The canonical CLI YouTube/multi-site extractor that several skills depend on for transcripts, audio, and video. Surfaced here because skills above won’t work fully without it on $PATH.

Key Takeaways

  • Plugins solve the distribution and versioning problem that raw skill files cannot: auto-updates, dependency management, and discovery
  • The official registry (101 plugins) covers the most common integrations — check there first
  • Community registries (SkillsMP, TokRepo, awesome-claude-skills) have massive catalogs but require manual vetting
  • Enterprise teams should use LiteLLM AI Gateway for private registries with governance controls
  • Creating a marketplace is as simple as adding a marketplace.json to a Git repo

Try It

  1. Run /plugin marketplace in Claude Code to browse the official registry
  2. Install one plugin that addresses a current workflow gap (e.g., Playwright for browser testing, Figma for design handoff)
  3. Check community registries (SkillsMP, TokRepo) if the official registry does not have what you need
  4. For team use: create a private marketplace by adding .claude-plugin/marketplace.json to an internal repo
  5. On Enterprise plans: set up a LiteLLM AI Gateway private registry for org-wide plugin governance

Open Questions

  • How does plugin auto-update handle breaking changes? Is there a version pinning mechanism for production stability?
  • What is the review/approval process for partner plugins in the official registry?
  • Can plugins declare dependencies on other plugins?

Graph View

Backlinks