| name | kg-broker |
| skill_type | skill |
| description | Thin verb over the engine's AMQP-style message broker — declare exchanges/queues, bind, publish, consume, and inspect stats. Use for engine-level queue/stream messaging (distinct from the agent bus) — "publish to this exchange", "consume the queue", "declare a queue". |
| license | MIT |
| tags | ["graph-os","engine","broker","messaging"] |
| tier | core |
| metadata | {"author":"Genius","version":"0.1.0"} |
kg-broker
Condensed intent-surface note (Seam 8). Under the default intent surface (MCP_TOOL_MODE=intent), graph_broker is held back from the default tool list (nothing removed — REST + _execute_tool still reach it exactly as documented below). Two ways to use this skill unchanged: (1) load_tools(tools=["graph_broker"]) once per session (as below), then proceed exactly as documented; or (2) call the act intent verb with the same natural-language request — the resolver routes to graph_broker for you and returns the result plus a routing justification. Set MCP_TOOL_MODE=condensed/verbose/both to expose the granular tools eagerly instead.
graph_broker (CONCEPT:AU-KG.coordination.engine-message-broker) is action-routed 1:1 over the engine broker surface (exchanges + queues + streams), distinct from the agent-to-agent kg-bus. Set action to the broker method: declare_exchange (+exchange_type), declare_queue, bind (queue+exchange[+routing_key]), publish (exchange+routing_key+payload), consume (queue[+max_messages,ack via params_json]), stats/list_queues/list_exchanges. Degrades cleanly when the engine build has no broker.
Invoke
- MCP:
load_tools(tools=["graph_broker"]), then graph_broker(action="publish", exchange="ex", routing_key="k", payload="hi").
- REST twin:
POST /graph/broker with {"action": "consume", "queue": "q", "params_json": "{\"max_messages\":10,\"ack\":true}"}.
Example
graph_broker(action="declare_queue", queue="jobs")
