v5.0.0 · curated & CI-validated

The orchestration layer
for Claude Code.

A curated marketplace of enterprise plugins — multi-agent teams, infrastructure automation, design systems, and domain expertise. Install only what you need, drop it into Claude Code, and ship.

Get started Browse the catalog
Plugins
35
Agents
261
Skills
250
Commands
294
MCP servers
8

Why this marketplace

Built like infrastructure, not a plugin dump

🧩

Composable, not monolithic

Install only the plugins you need. Claude Code loads commands, skills, and agents lazily, so context stays lean even with the whole catalog enabled.

🛡️

CI-validated, every PR

One workflow validates manifests, frontmatter, MCP entry points, and schemas. If a plugin is listed here, it loaded cleanly — no cache errors.

🤖

Multi-agent by design

261 role-scoped agents and ready-made teams. Orchestration patterns — councils, pipelines, swarms — are first-class, not bolted on.

🔌

MCP-native

8 plugins ship Model Context Protocol servers, giving Claude live tools for Jira, Microsoft Graph, deployments, diagrams, and more.

The catalog

Every plugin, one search away

Filter by category, search by name or capability, then expand any card for the full breakdown. Counts are generated directly from the marketplace manifest — never stale.

Curated stacks

Opinionated bundles to start fast

Not sure where to begin? Each stack groups plugins that work well together. Click any stack to filter the catalog to its members.

How it works

From manifest to multi-agent run in three moves

  1. 1

    Add the marketplace

    Point Claude Code at this repository's manifest once. Every plugin becomes discoverable through /plugin.

    /plugin marketplace add markus41/claude
  2. 2

    Install what you need

    Each plugin is self-contained — its own commands, skills, agents, and MCP servers. No monolith, no bloat.

    /plugin install jira-orchestrator
  3. 3

    Orchestrate

    Invoke a command or let an agent team take over. Skills activate on intent; hooks enforce your rules.

    /jira-ship  → a council of agents plans, codes & reviews

Anatomy of a plugin

Four building blocks, composable by design

Every plugin is a thin manifest over four primitives. Claude Code loads them lazily, so context stays lean even with the full catalog installed.

⌘

Commands

Single-intent slash commands. Deterministic entry points like /deploy or /jira-work.

294 across the catalog
✦

Skills

Behavior-triggering knowledge that activates on intent — no command needed. Progressive disclosure for the model itself.

250 skills installed
◎

Agents

Specialized sub-agents with scoped tools and models. Compose into teams for parallel, role-based work.

261 role-scoped agents
⚙

MCP & Hooks

Model Context Protocol servers add live tools; lifecycle hooks enforce rules and capture lessons.

8 plugins ship MCP servers
See the on-disk plugin layout 
plugins/<plugin-name>/
├── .claude-plugin/
│   └── plugin.json        # manifest: name, version, author, keywords
├── commands/              # *.md  — one slash command per file
│   └── <command>.md
├── skills/
│   └── <skill-name>/
│       └── SKILL.md        # frontmatter + instructions
├── agents/                # *.md  — YAML frontmatter (name, model, tools)
│   └── <agent>.md
├── hooks/                  # lifecycle scripts (PreToolUse, SessionStart…)
└── mcp/ or src/mcp/        # optional Model Context Protocol server

Every command, skill, agent, and hook file must carry YAML frontmatter (at minimum description:). Missing frontmatter is the #1 cause of plugin cache errors — and exactly what the CI validator catches on every PR.

Installation

Up and running in under a minute

Inside Claude Code

The fastest path — no clone required.

# 1 · register this marketplace
/plugin marketplace add markus41/claude

# 2 · browse what's available
/plugin

# 3 · install a plugin
/plugin install claude-code-expert

For contributors

Validate locally with the same check CI runs.

# clone & install dev tooling
git clone https://github.com/markus41/claude
cd claude && pnpm install

# validate the whole marketplace
pnpm check:marketplace
Sub-marketplace plugins (advanced)

Six additional plugins live under .claude/plugins/ — available but not installed by default:

    Quality & trust

    Every plugin passes the gate before it ships

    A single GitHub Actions workflow — Marketplace CI — validates the entire catalog on every pull request. If it's in the marketplace, it loaded cleanly.

    ✓

    Manifest integrity

    Every source resolves to a real plugin manifest with required fields.

    ✓

    Frontmatter coverage

    Every command, skill, agent & hook file carries valid YAML frontmatter.

    ✓

    No phantom MCP entrypoints

    MCP servers can't reference gitignored build artifacts like dist/.

    ✓

    TypeScript strict

    tsc --noEmit passes on all dev tooling under scripts/ and types/.

    ✓

    Schema-validated archetypes

    Every example archetype validates against its JSON Schema (Draft 7).

    ✓

    No tracked node_modules

    A dedicated guard keeps dependency trees out of the repository.