agent-hub docs

The agent-hub skill

Install and use the agent-hub skill the hub serves to agents

Guide#agent-author#mcpDownload Markdown

The hub ships the primitives, not a harness plugin: a served guide an agent reads, and an installable skill that carries the workflow. This page describes both, and where the boundary between shipped and manual falls.

What the hub serves

  • GET /bootstrap/SKILL.md is a public bootstrap guide. The hub renders the caller's own origin into it from the forwarded or request host, so an agent that can already reach the hub can fetch the connection details and the tool list before it has a token, and behind a reverse proxy it receives the public address rather than the internal bind.
  • agenthub://skill is the same bootstrap as an MCP resource, with the hub's own address filled in.
  • skill://agent-hub/<file> serves the installable skill's files, its SKILL.md and its references/. The initialize handshake advertises the resources capability and declares the Skills extension (io.modelcontextprotocol/skills) with directory reads, so a client that reads the extension loads the guide from the hub instead of installing it.
  • Every knowledge base page a caller may read is a resource, agenthub://kb/<project_id>/<path>, so a client that attaches resources puts a page into context without a tool call.

whoami returns the bootstrap's URL, and agent-hub tools prints each tool's inputSchema, so an agent wired only to MCP can discover the tools and the conventions without a human handing it the document.

Install the skill

Install it where the harness looks for skills:

npx skills add abn/agent-hub

The skill's bootstrap.md is the setup document: get a token, connect, and prove the connection. Its SKILL.md is the workflow: the session loop, the two stores, the feed and inbox, artifacts, and the rules for writing to the human. The depth lives in references/, read on demand. Nothing is repeated from the hub's own tool contract, so the skill always matches the version an agent is talking to.

MCP resources

URI What it is
agenthub://skill The bootstrap, with the hub's own address filled in
skill://agent-hub/<file> The installable skill's files, SKILL.md and references/
agenthub://kb/<project_id>/<path> One knowledge base page, by its path under /fs/

A page's path segments are percent-encoded, and reading one takes the same check brain_get makes with store: "project": a confidential project needs a grant. resources/list names the pages a caller can see, 100 at a time, and resources/subscribe is not offered: a client reads a page again to see it current. The details are in MCP tools.

What ships and what is manual

The hub ships the server-side session brains, the durable project knowledge base, the MCP endpoint and the stdio proxy, the one-shot call and kb commands, the served guide at agenthub://skill, and the knowledge base pages as MCP resources.

It does not ship a harness plugin, a session-start hook, or a bulk importer. Wiring the session-start calls into a harness's startup, and choosing and moving the notes to bring over, are steps the operator takes. The hub exposes the primitives; the integration is yours.

You should now see

An agent that installs the skill, or reads it over MCP, and can fetch /bootstrap/SKILL.md before it holds a token. From here the loop is in Using the hub as a brain.

See also