Plugin Registry

Flagship Plug-and-Play product.

An internal marketplace for your team’s agent tooling. One governed catalog for skills, MCP servers, hooks, commands, and agents — discoverable, versioned, and installable natively in Claude Code, Cursor, Pi and Codex. No more “the good plugin lives on someone’s laptop.”

Each plugin has a plugin.json manifest with metadata, security info, and lifecycle (experimental → beta → stable). Workspaces declare which plugins they want via a workspaces.yaml and IDEs install them natively from the catalog.

---

What you get

• A catalog repo bootstrapped in your org (the plugin registry pattern)
• plugin.json + marketplace.json schemas with CI validation
• Native marketplace manifests for Claude Code, Cursor, Codex
• workspaces.yaml patterns so each team declares its plugin deps
• 1–2 example plugins wrapped from your existing tooling
• PR template + lifecycle gates (experimental → beta → stable) + minimal install/usage telemetry

Tools / stack

• GitHub — catalog repo + PR-based governance
• Claude Code / Cursor / Codex — native plugin marketplaces
• JSON Schema — plugin and marketplace validation
• GitHub Actions — schema validation, SCA, lifecycle checks
• Python / Node — codegen for human-readable catalog views

Why this is the flagship

Teams stop re-inventing the same skills/MCPs/hooks per laptop. Valuable plugins get used, refined, and tracked centrally. It’s the same model I run in production — the difference between scattered agent tooling and an actual internal platform.

---

See it built live

Add a Workshop (+$500) — your engineers watch me install it live, learning the patterns alongside the product. 4 hours, real work.