One entry point for the whole RuV stack: marketplace, skills, read only CLI

Why an entry point

The stack has grown past the point where a README list is useful. This commit turns the profile repository into something installable: a marketplace of plugins, a set of skills, and a companion that can read the stack without changing anything.

What changed

The commit adds the RuV Stack marketplace, the skills bundle and a read only CLI and MCP entry point. Read only is the point: discovery should never need write authority.

The README also documents remote federation endpoints, which you add as a remote MCP server and authorize when prompted. There are two, and which one you use depends on the client.

Get started

In Claude Code, add the marketplace and install the plugin:

/plugin marketplace add ruvnet/ruvnet
/plugin install ruvnet@ruvnet

Expected result: the RuV Stack commands and skills appear in your Claude Code session.

For federation, add the endpoint for your client as a remote MCP server and authorize when prompted. The install guide lists a different address for ChatGPT than for Claude chat and Lovable, so check which one applies before you paste it:

ChatGPT:                 https://x.ruv.io/chatgpt/mcp
Claude chat and Lovable: https://x.ruv.io/mcp

Do not paste credentials into a command; the client handles authorization. The local companion is a separate route and needs Node.js 22 or newer.

Use it today

Practical case: you want to evaluate the stack before committing to it. Install the marketplace plugin, browse what each component claims, and only then clone the one repository you actually need.

Acceptance test: after install, list your plugins and confirm ruvnet appears. If it does not, the marketplace add step did not complete.

Push it further

Experimental commentary. A shared federation endpoint is where the stack stops being a collection of tools and starts being an organisation of agents. The dependency is authorization: anything that coordinates across machines has to be explicit about what it can reach.

Falsifiable test: connect, then try to perform a write your session was never authorized for. It should fail cleanly.