Bout Labs — Claude Code plugins

The marketplace for Bout Labs' Claude Code plugins. One repo, one marketplace.json, however many plugins we end up shipping.

Install

In any Claude Code session:

/plugin marketplace add BoutLabs/claude-plugins
/plugin install cornerman@bout-labs

The marketplace name is bout-labs (the slug after @ in install commands); the repo name is claude-plugins (what /plugin marketplace add resolves).

What's in the marketplace

cornerman — the team in your corner

The agent loop + skills + project scaffolding we run across every codebase. Drop it into a repo, run /bootstrap-project, and you get:

• Agent pipeline — spec-writer → architect → implementer → pr-reviewer → ci-fixer, wired against GitHub Issues, Projects, and branch protection
• Observability substrate — machine-checkable hand-off contracts, structured telemetry stream, per-step watchdogs with incident capture, verified-mutations invariant
• Loop-quality agents — qa-tester, learnings-extractor, post-merge, plus dial controls (--dry-run, capabilities/features, API budget, trust budget)
• Skills — /cornerman retro, /cornerman where-am-i, /cornerman resume for telemetry aggregation, per-issue resumability, and full session restoration
• Stack presets — iOS / Xcode, Next.js, Python (Poetry), each with their own commands + timeouts + capabilities + known gotchas
• Tracker backends — GitHub Projects v2, Linear, or text-files fallback for projects without an external tracker

Currently pinned at v0.3.0. See the cornerman repo for the full README, schema docs, and changelog.

Adding a new plugin to the marketplace

For Bout Labs maintainers:

1. Ship your plugin in its own repo with a .claude-plugin/plugin.json manifest (cornerman is the canonical example)

2. Cut a release on that repo (tag + GitHub release; pin a SHA)

3. Append an entry to .claude-plugin/marketplace.json in this repo:

   {
     "name": "<plugin-name>",
     "description": "<one-paragraph pitch>",
     "author": { "name": "Bout Labs" },
     "category": "<see schema>",
     "tags": ["..."],
     "source": {
       "source": "github",
       "repo": "BoutLabs/<your-plugin-repo>",
       "ref": "v0.1.0",
       "sha": "<commit sha of the tag>"
     },
     "homepage": "/BoutLabs/<your-plugin-repo>"
   }

4. PR-and-merge to update the marketplace

The marketplace repo's release cadence is independent — only update marketplace.json when one of the plugins ships a new version.

Updating a plugin's pinned version

When a plugin cuts a new release, bump that plugin's source.ref (to the new tag) and source.sha (to the new commit SHA) in marketplace.json. Users get the new version on their next /plugin update.

Schema

The marketplace file follows Anthropic's Claude Code marketplace schema. See the official docs for the full reference.

License

Each plugin carries its own license in its source repo. This marketplace repo (the listing metadata) is intentionally permissive — fork it, learn from it, use the structure for your own org's marketplace.