Summary
Distribute relay as a first-class Claude Code plugin using the native .claude-plugin marketplace format. Users would add the repo as a marketplace and install the plugin in two slash commands instead of cloning + running install.sh.
What this looks like
Add two manifests to the repo:
.claude-plugin/marketplace.json at repo root — declares this repo as a Claude Code marketplace that publishes one or more plugins.
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "relay",
"version": "1.0.0",
"description": "Multi-agent coordination for Claude Code, Codex, Gemini, and more.",
"owner": { "name": "AgentWorkforce" },
"plugins": [
{
"name": "relay",
"source": "./plugin/relay",
"description": "...",
"category": "productivity",
"homepage": "https://github.com/AgentWorkforce/relay"
}
]
}
plugin/relay/.claude-plugin/plugin.json — the plugin's own manifest (name, version, author, license, keywords).
Inside plugin/relay/, symlink or copy what we want to ship: skills, slash commands, hooks, and any MCP server registration.
What to bundle (initial cut)
- Skills — the agent-relay coordination skills under
skills/ (orchestrating-agent-relay, using-agent-relay, etc.).
- Slash commands — at minimum a
/relay-install-hooks command that wires up the relay CLI and (eventually) writes the Claude Code hook entries.
- MCP server — register the relaycast MCP stdio server so
mcp__relaycast__* tools are available out of the box without users hand-editing settings.
- Optional — bundled agents (lead, worker personas).
User flow
/plugin marketplace add github.com/AgentWorkforce/relay
/plugin install relay
Done — skills, slash commands, and the relaycast MCP server are all wired up, no clone, no install.sh.
Out of scope
- The Rust broker binary itself still installs via existing channels (npm, install.sh). The plugin layers on top.
- No changes to the existing PRPM packaging — both can coexist; the Claude Code plugin path is for users who live in
/plugin.
Effort
Small — mostly deciding what to bundle and writing the two manifest files. ~1–2 hours for a minimal version that ships skills + the relaycast MCP server registration.
Summary
Distribute relay as a first-class Claude Code plugin using the native
.claude-pluginmarketplace format. Users would add the repo as a marketplace and install the plugin in two slash commands instead of cloning + runninginstall.sh.What this looks like
Add two manifests to the repo:
.claude-plugin/marketplace.jsonat repo root — declares this repo as a Claude Code marketplace that publishes one or more plugins.{ "$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "relay", "version": "1.0.0", "description": "Multi-agent coordination for Claude Code, Codex, Gemini, and more.", "owner": { "name": "AgentWorkforce" }, "plugins": [ { "name": "relay", "source": "./plugin/relay", "description": "...", "category": "productivity", "homepage": "https://github.com/AgentWorkforce/relay" } ] }plugin/relay/.claude-plugin/plugin.json— the plugin's own manifest (name, version, author, license, keywords).Inside
plugin/relay/, symlink or copy what we want to ship: skills, slash commands, hooks, and any MCP server registration.What to bundle (initial cut)
skills/(orchestrating-agent-relay, using-agent-relay, etc.)./relay-install-hookscommand that wires up the relay CLI and (eventually) writes the Claude Code hook entries.mcp__relaycast__*tools are available out of the box without users hand-editing settings.User flow
Done — skills, slash commands, and the relaycast MCP server are all wired up, no clone, no install.sh.
Out of scope
/plugin.Effort
Small — mostly deciding what to bundle and writing the two manifest files. ~1–2 hours for a minimal version that ships skills + the relaycast MCP server registration.