Claude Code Plugin Marketplace

A curated marketplace of Claude Code plugins covering cloud infrastructure, enterprise SaaS, documentation intelligence, project management, frontend design systems, and more. Each plugin ships its own commands, skills, agents, and (where relevant) MCP servers.

🌐 Browse the marketplace → markus41.github.io/claude — a searchable catalog with live counts, category filters, and per-plugin detail. The site is generated directly from marketplace.json and deployed via GitHub Pages.

Installation

Install the marketplace and then enable individual plugins through Claude Code:

# In Claude Code
/plugin install <plugin-name>

Or point Claude Code at this repository's .claude-plugin/marketplace.json:

/plugin marketplace add <url-to-this-repo>

Plugins

Plus six sub-marketplace plugins available under ./.claude/plugins/: langgraph-architect, code-quality-orchestrator, api-integration-helper, dev-environment-bootstrap, migration-wizard, testforge.

CI Validation

Every pull request runs the Marketplace CI workflow, which validates:

• .claude-plugin/marketplace.json parses cleanly and every source resolves to a plugin manifest
• Every plugin's plugin.json has required fields (name, version, description, author)
• Every command/agent/skill/hook file referenced from a manifest exists and has YAML frontmatter
• No MCP server entry point references a gitignored build artifact (e.g., dist/cli.js)
• Every auto-discovered .md file under commands/, agents/, hooks/, and every skills/*/SKILL.md has YAML frontmatter
• TypeScript strict check passes on scripts/ and types/
• Every archetype example in examples/archetypes/ validates against the schema

Missing frontmatter is the most common cause of Claude Code cache errors — the CI validator catches this for every plugin before merge.

Repository Layout

.
├── .claude-plugin/
│   └── marketplace.json        # Marketplace manifest (27 plugins)
├── plugins/                    # 22 installed plugins
├── .claude/
│   ├── plugins/                # 6 sub-marketplace plugins
│   ├── agents/                 # Platform-level agents
│   ├── skills/                 # Platform-level skills
│   ├── hooks/                  # Lifecycle hook scripts
│   ├── rules/                  # Behavioral rules (always loaded)
│   ├── registry/               # Plugin index and search metadata
│   └── mcp-servers/            # Custom MCP servers
├── scripts/                    # Plugin-dev tooling (validation, indexing)
├── schemas/                    # JSON Schemas for plugins and archetypes
├── docs/                       # Context and architecture documentation
└── examples/                   # Reference archetypes

Plugin Development

Validate every plugin and the marketplace manifest before committing:

pnpm install
pnpm check:marketplace         # Validate marketplace + every plugin (the primary check)
npx tsc --noEmit               # Type-check scripts/ and types/
pnpm validate-archetype <file> # Validate an archetype example against the schema
pnpm profile:plugin-context    # Measure per-plugin context overhead

See plugins/claude-code-expert for in-depth plugin authoring guidance.

Marketplace Site

The public catalog at markus41.github.io/claude is a self-contained static site under site/. Its plugin data is generated from .claude-plugin/marketplace.json and the per-plugin manifests — counts never drift from the source of truth.

pnpm build:site        # regenerate site/data/plugins.json from the manifest
# preview locally
npx serve site         # or: python3 -m http.server -d site 8080

The Deploy GitHub Pages workflow (.github/workflows/pages.yml) rebuilds the data and publishes site/ whenever the manifest, a plugin manifest, or the site changes on main.

First-time setup (one-time): enable Pages at Settings → Pages → Build and deployment → Source: GitHub Actions. The workflow's GITHUB_TOKEN can deploy to Pages (pages: write) but cannot create the Pages site — that needs repo-admin, so the initial enablement must be done in the UI. Until then the workflow detects the missing Pages site and skips the deploy with a notice instead of failing, so main stays green. Once Pages is enabled, every push to main deploys automatically (or re-run the workflow to publish immediately).

Contributing

1. Scaffold a new plugin with the claude-code-templating generator or copy an existing plugin as a template.
2. Add frontmatter (description: at minimum) to every command, skill, agent, and hook file — missing frontmatter produces cache errors when Claude Code loads the plugin.
3. If the plugin declares an mcpServers entry point, commit the built artifact or wire it to a postinstall hook — gitignored dist/ paths will fail validation.
4. Update .claude-plugin/marketplace.json with your plugin entry.
5. Run pnpm check:marketplace before opening a PR — this is the same check CI runs.

License

MIT — see LICENSE.