Bring an existing agent

Create the HubCopy Anchor Link

hubzoid init ops-briefing

Run it in a new folder, outside your existing project. It writes a runnable Hub with one example of each file type and a .env with a random bridge key. Delete the examples you will not use, then copy your files in as below. See quickstart for installing Hubzoid and choosing a model.

Turn CLAUDE.md into AGENTS.mdCopy Anchor Link

Copy the parts of CLAUDE.md that describe the work: the goal, the rules, the tone, when to use what. Leave out build commands and coding conventions that only mattered to you in an editor. Add frontmatter for the name the team will see and a few starter prompts.

---
name: ops-briefing
description: Daily Reports and supplier follow-up for the operations lead.
suggestions:
  - Prepare today's daily report
  - Which supplier orders are late?
---

You prepare the operations lead's daily report for a home goods retailer
with four stores (north, south, east, west).

- Use the daily-reports skill for the daily briefing.
- Get open orders from the open_orders tool. Never estimate a quantity.
- Escalate according to the escalation-policy knowledge document.
- For questions about a supplier's record, use the supplier-research agent.

Replace @docs/escalation-policy.md style imports with a sentence that names the knowledge document, and move the document to knowledge/escalation-policy.md. The agent sees a menu of knowledge documents and reads one with read_knowledge when it needs it.

Move skills and commandsCopy Anchor Link

Copy .claude/skills/daily-reports/ to skills/daily-reports/. The SKILL.md frontmatter works unchanged. Supporting files are not loaded with the skill, so point to them by their path from the Hub root:

---
name: daily-reports
description: Build the daily report for the operations lead.
---

1. Read the layout in skills/daily-reports/template.md with read_file.
2. Call open_orders and list orders due today or overdue, by store.
3. Apply the escalation policy and put anything that needs a decision first.

A command such as .claude/commands/weekly-review.md becomes skills/weekly-review.md with name and description frontmatter. Hubzoid does not substitute $ARGUMENTS, so write the command as instructions that use whatever the person asked.

Move sub-agentsCopy Anchor Link

Copy .claude/agents/supplier-research.md to agents/supplier-research.md and adjust two keys:

---
name: supplier-research
description: When the user asks about a supplier's delivery record or recent news.
model: claude-local/opus
tools: [web_search, http_get, read_knowledge]
---

Research the supplier with web_search and http_get and reply with a short,
sourced summary of delivery issues and news from the last 90 days.

• tools: must be a YAML list of Hubzoid tool names. A comma-separated string such as Read, Grep stops the Hub from building, and Claude Code tool names do not exist in Hubzoid.
• model: must be a Hubzoid model id, or be removed. Claude Code aliases such as sonnet, opus or inherit are not Hubzoid ids. A sub-agent whose model differs from the Hub's on the same engine runs on its own model as a delegate. Otherwise it is loaded into the main agent as a skill, and its tools: list is ignored.

Move MCP serversCopy Anchor Link

Move .mcp.json to connectors/.mcp.json. Local (stdio) servers work as they are. For an HTTP server, replace "type": "http" with "transport": "streamable-http", because a server with a url and no transport is treated as SSE. Hubzoid expands ${NAME} but not ${NAME:-default}, so set every variable in the Hub's .env.

{
  "mcpServers": {
    "inventory": {
      "type": "http",
      "url": "${INVENTORY_MCP_URL:-https://mcp.example.com/mcp}",
      "headers": { "Authorization": "Bearer ${INVENTORY_TOKEN}" }
    }
  }
}

{
  "mcpServers": {
    "inventory": {
      "transport": "streamable-http",
      "url": "${INVENTORY_MCP_URL}",
      "headers": { "Authorization": "Bearer ${INVENTORY_TOKEN}" }
    }
  }
}

In a Hub, everyone who uses the agent shares the connector's credential. If each person should act with their own account, see per-user MCP servers.

Turn scripts into toolsCopy Anchor Link

In Claude Code the agent ran python scripts/open_orders.py in a shell. A Hub agent has no shell, so move the logic into a tool:

"""Open supplier orders, moved from scripts/open_orders.py."""
from __future__ import annotations

import csv
import json
from pathlib import Path

from agents import function_tool

ORDERS = Path(__file__).resolve().parent.parent / "raw_data" / "orders.csv"


@function_tool
def open_orders(supplier: str = "") -> str:
    """Open supplier orders with their store and due date.

    Args:
        supplier: Only this supplier. Leave empty for all suppliers.

    Returns:
        JSON list of open orders.
    """
    with ORDERS.open(newline="", encoding="utf-8") as f:
        rows = [r for r in csv.DictReader(f) if r["status"] == "open"]
    if supplier:
        rows = [r for r in rows if r["supplier"].lower() == supplier.lower()]
    return json.dumps(rows)

Tool files are loaded one by one rather than as a package, so a tool cannot import a sibling file from tools_local/. Keep each tool file self-contained, or install shared code as a package. See tools and connectors.

Schedule the briefingCopy Anchor Link

What you started by hand each morning can now run on its own. Scheduled tasks are Markdown files:

---
schedule: "30 7 * * 1-6"
write: ["briefings/"]
---

Prepare today's daily report with the daily-reports skill and save it
to briefings/today.md.

The task runs at 07:30 server time from Monday to Saturday with the same agent, skills and tools as chat. See markdown tasks.

Check itCopy Anchor Link

Add an eval that proves the briefing uses real order data, then run the checks:

---
expect_tools: [open_orders]
---
## Prompt
Prepare today's daily report.

## Criteria
Lists overdue orders by store from the tool result. Does not invent quantities.

hubzoid doctor ./ops-briefing
hubzoid test ./ops-briefing --prompt "Which supplier orders are late?"
hubzoid eval run ./ops-briefing
hubzoid run ./ops-briefing