Name: acp-bridge-caller
Author: xiwan

Imported from xiwan/acp-bridge (skill/SKILL.md). Install upstream with npx skills add xiwan/acp-bridge --skill skill. Copyright stays with the author.

ACP Bridge Caller

Call remote CLI agents via ACP Bridge HTTP API.

Auth (required)

export ACP_BRIDGE_URL=<bridge_url>
export ACP_TOKEN=<token>
ACP_CLIENT="${CLAUDE_SKILL_DIR:-$(dirname "$0")}/scripts/acp-client.sh"
chmod +x "$ACP_CLIENT"

If either ACP_BRIDGE_URL or ACP_TOKEN is missing, stop and ask the user. Never echo the token.

Init Check (auto, first use only)

$ACP_CLIENT -l

Display as: 🌉 ACP Bridge connected — Agents: kiro ✅ · claude ✅ · hermes ✅ ...

If fails → show error and stop. If succeeds → cache, skip on subsequent requests.

Message Routing

First match wins:

/hb → Heartbeat monitor (see references/heartbeat.md)
/chat → Chat command (see references/chat.md)
/cli → Single CLI call
chat-state.json exists → Forward to current agent
Fallback → Normal processing (no Bridge call)

Planning (for multi-agent / pipeline / async tasks)

For natural-language tasks, classify → pick agents → present plan → execute. Full workflow: references/planning.md

Quick rules:

Single verb, one agent, ≤60s → /cli xx "..." directly, no plan needed
Multiple agents / "first X then Y" / "discuss" → Pipeline, show plan first
Estimated >60s → must be async (POST /jobs)
Harness presets & model compatibility → references/harness-presets.md

Output Rules — Faithful Relay

You are a messenger, not an editor.

MUST: show agent output as-is (including errors), attribute with 🤖 <agent> replied:, let user decide on failure
MUST NOT: rewrite / summarize / complete the task yourself / mix analysis into the agent reply

Commentary allowed after full output, separated with --- and prefixed 💬 My note:.

Commands (aliases)

./cli <prompt> (default agent) · ./cli ko|cc|cx|qw|oc|hm|hf|og "..." (kiro / claude / codex / qwen / opencode / hermes / harness / opengame) · /chat ko|cc [--cwd <path>] (enter) · /chat end|status · /upload <file> · /hb [status|logs|ping|ctx] (heartbeat)

References

references/planning.md — Full planning workflow (Steps 1–7)
references/harness-presets.md — Preset capability matrix, model compatibility
references/heartbeat.md — Heartbeat monitor, agent activity observation
references/chat.md — Chat mode lifecycle, session ID, state file
references/pipeline.md — Pipeline API, modes, conversation config
references/orchestration-patterns.md — Preset templates for 2–5 agent orchestration
references/async-jobs.md — Async jobs, target format, callback, monitoring
references/troubleshooting.md — Error diagnosis
references/usage.md — LiteLLM usage tracking, token/cache stats
scripts/acp-client.sh — Bash client used by /cli and /chat
AGENT.md — First-time setup guide

Install acp-bridge-caller and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "xiwan-acp-bridge-skill", "kind": "skill", "name": "acp-bridge-caller", "description": "v0.46.0 — ALWAYS USE THIS SKILL when user mentions: kiro/claude/codex/acp/bridge/harness/hermes/openclaw/opengame/aws-devops/agent Task/Orchestration or anything similar", "publisher": "xiwan", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "v0.46.0 — ALWAYS USE THIS SKILL when user mentions: kiro/claude/codex/acp/bridge/harness/hermes/openclaw/opengame/aws-devops/agent Task/Orchestration or anything similar" ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/xiwan/acp-bridge", "path": "skill/SKILL.md", "ref": "b01b9cf8eb4746e97807ce40c1fd1b9f19f0aad7", "url": "https://github.com/xiwan/acp-bridge/blob/b01b9cf8eb4746e97807ce40c1fd1b9f19f0aad7/skill/SKILL.md", "key": "xiwan/acp-bridge/skill/SKILL.md" } }, "instructions": "# ACP Bridge Caller\n\nCall remote CLI agents via ACP Bridge HTTP API.\n\n## Auth (required)\n\n```bash\nexport ACP_BRIDGE_URL=<bridge_url>\nexport ACP_TOKEN=<token>\nACP_CLIENT=\"${CLAUDE_SKILL_DIR:-$(dirname \"$0\")}/scripts/acp-client.sh\"\nchmod +x \"$ACP_CLIENT\"\n```\n\nIf either `ACP_BRIDGE_URL` or `ACP_TOKEN` is missing, **stop and ask the user**. Never echo the token.\n\n## Init Check (auto, first use only)\n\n```bash\n$ACP_CLIENT -l\n```\n\nDisplay as: `🌉 ACP Bridge connected — Agents: kiro ✅ · claude ✅ · hermes ✅ ...`\n\nIf fails → show error and stop. If succeeds → cache, skip on subsequent requests.\n\n## Messa", "cost": { "context_tokens": 789 } }

acp-bridge-caller

About