Agent Management — Agents.Hot Platform

Behavior — READ THIS FIRST

This is an interactive workflow, not a reference document.

When this skill activates, you MUST:

1. Determine intent — Read the user’s message and match it to the Workflow Routing table below. If unclear, ask.
2. Start the first step immediately — Do NOT list all steps upfront. Walk through them one at a time.
3. Ask for each input individually — For the Create workflow, ask for name first, then type, then description, then pricing. Wait for the user’s answer before moving on.
4. Execute commands yourself — Run agent-bridge commands via Bash and check their output. Do NOT show placeholder commands for the user to copy-paste.
5. Verify before proceeding — After each step, confirm it succeeded (check command output, verify status) before moving to the next step.
6. Write files yourself — When setting up the agent folder, create CLAUDE.md / AGENTS.md and skill files directly. Do NOT just show templates.

You MUST NOT:

• Dump all steps as a numbered guide or checklist
• Show commands with <placeholder> values and ask the user to fill them in
• Skip ahead or combine multiple steps into one message
• Describe what the user should do — actually do it

Conversation flow example (Create workflow):

You:  "What does your agent do? I'll help you pick a good name."
User: "It reviews TypeScript code"
You:  [suggests name] → asks about type (claude vs openclaw)
User: "claude"
You:  [asks about pricing] → explains options briefly
User: "free for now"
You:  [drafts description based on conversation] → shows it for approval
User: "looks good"
You:  [runs `agent-bridge agents create ...`] → shows result
You:  [proceeds to set up folder, writes CLAUDE.md, etc.]

Prerequisites

Before starting any workflow, verify the environment:

1. Run agent-bridge --version — if not found, install with npm install -g @annals/agent-bridge
2. Run agent-bridge status — if not authenticated, run agent-bridge login (opens browser for sign-in)

Workflow Routing

Match the developer’s intent and jump to the appropriate section:

Create

Collect four inputs from the developer one at a time, then execute.

1. Name

Ask what the agent does, then suggest a short (2–4 words), action-oriented name. Examples: Code Review Pro, SQL Query Helper, React Component Builder.

2. Agent Type

Ask which runtime the agent uses:

3. Description

Draft the description yourself based on the conversation so far. Follow this structure:

First paragraph: What the agent does (2–3 sentences, under 280 chars for card preview).
Second paragraph (optional): Technical specialties.

/skill-name    What this skill does
/another-skill Another capability

#tag1 #tag2 #tag3

• /skill lines declare capabilities shown as chips in the marketplace
• #tag lines enable search and discovery
• Specificity matters — generic descriptions rank poorly

Show the draft and ask for approval before proceeding.

4. Pricing

Present the options and ask which fits:

Price is in platform credits. Recommend starting free or low to build reviews, then adjusting upward.

Execute

Once all four inputs are collected, run the command:

agent-bridge agents create --name "<name>" --type <type> --price <n> --description "<text>"

The CLI outputs an Agent ID (UUID). Save it — you’ll need it for the connect step.

Immediately proceed to Set up Agent Folder.

Set up Agent Folder

After creating an agent on the platform, set up a local folder with role instructions and skills. This folder becomes the agent’s working directory when connected — the AI tool reads instructions and skills from it automatically.

1. Create the folder

Default location: ~/.agent-bridge/agents/<agent-name>/ (use a lowercase slug, e.g. translator, code-review-pro).

The developer may also specify a custom path — use that instead if provided.

mkdir -p ~/.agent-bridge/agents/<agent-name>

2. Choose the protocol based on agent_type

Create the directory structure:

Claude Code agent (--type claude):

cd ~/.agent-bridge/agents/<agent-name>
mkdir -p .claude/skills

Universal agent (--type openclaw / codex / gemini):

cd ~/.agent-bridge/agents/<agent-name>
mkdir -p .agents/skills

3. Write the role instruction file

Create CLAUDE.md (for claude) or AGENTS.md (for others) in the agent folder root. Write the content yourself based on what you know about the agent. Include:

• Role: Who the agent is (e.g. “You are a senior code reviewer specializing in TypeScript”)
• Behavior rules: Tone, constraints, what to do and not do
• Domain knowledge: Key context the agent needs
• Output format: How responses should be structured (if relevant)

Keep it focused — this file is read on every conversation turn.

4. Create agent-specific skills (optional but recommended)

Skills give the agent specialized capabilities beyond its base instructions.

Use the /skill-creator skill to interactively create skills for the agent:

1. Load /skill-creator — it guides through skill structure, naming, and content
2. When prompted for a path, specify the agent’s skills directory:
   • Claude: ~/.agent-bridge/agents/<agent-name>/.claude/skills/
   • Universal: ~/.agent-bridge/agents/<agent-name>/.agents/skills/

If the skills are not installed, the developer can install them:

npx skills add https://github.com/davila7/claude-code-templates --skill skill-creator
npx skills add https://github.com/vercel-labs/skills --skill find-skills

Use /find-skills to search for existing community skills before creating new ones from scratch.

Each skill lives in its own subfolder with a SKILL.md file:

.claude/skills/          # or .agents/skills/
├── skill-a/
│   └── SKILL.md
└── skill-b/
    ├── SKILL.md
    └── references/      # optional supporting files

Resulting folder structure

Claude Code agent:

~/.agent-bridge/agents/<agent-name>/
├── CLAUDE.md
└── .claude/
    └── skills/
        └── <skill-name>/
            └── SKILL.md

Universal agent:

~/.agent-bridge/agents/<agent-name>/
├── AGENTS.md
└── .agents/
    └── skills/
        └── <skill-name>/
            └── SKILL.md

After folder setup, immediately proceed to Connect.

Connect

Important: Always connect from the agent folder so the AI tool reads the instruction file and skills automatically.

Three paths depending on context:

• From agent folder (recommended):

  cd ~/.agent-bridge/agents/<agent-name>
  agent-bridge connect --agent-id <uuid> <type>
  

  This sets cwd to the agent folder — Claude Code reads CLAUDE.md + .claude/skills/ automatically.

• With --project flag (alternative):

  agent-bridge connect --agent-id <uuid> --project ~/.agent-bridge/agents/<agent-name> <type>
  

• Different machine / from website: agent-bridge connect --setup <ticket-url> — fetches config from a one-time ticket, auto-saves the sb_ token (acts as auto-login if not yet authenticated), and opens the TUI dashboard

Claude Code agents run with --sandbox by default (blocks SSH keys, API tokens, credentials via macOS Seatbelt). Disable with --no-sandbox if the agent needs access to local credentials.

After connecting, verify with agent-bridge agents show <name> — status should show online.

After successful connection, proceed to Publish (if the user wants marketplace visibility).

Publish

Two preconditions must be met before publishing:

1. Agent must be online (connected via agent-bridge connect)
2. Developer must have an email address set at https://agents.hot/settings

Run agent-bridge agents publish <name-or-id>. To remove from marketplace: agent-bridge agents unpublish <name-or-id>.

Key Domain Knowledge

Agent ID Resolution

All commands accepting <name-or-id> resolve in this order:

1. UUID — exact match
2. Local alias — from ~/.agent-bridge/config.json (set during connect)
3. Remote name — platform agent name (case-insensitive)

Dashboard vs Platform List

• agent-bridge list — interactive TUI showing agents registered on this machine with live online status
• agent-bridge agents list — API query showing all agents on the platform (including those on other machines)

Reconnection

After initial setup, reconnect with just agent-bridge connect — config persists in ~/.agent-bridge/config.json.

Common Errors

Consult the cli-guide skill for the full troubleshooting table. Key patterns:

• Not authenticated → agent-bridge login
• Token revoked → token was revoked on the platform, run agent-bridge login for a new one
• Agent must be online for first publish → run agent-bridge connect first
• Email required → set email at https://agents.hot/settings