amq-clilisted

Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route messages across projects, or diagnose delivery issues. Also use it when you receive a message and need to know how to reply, inspect receipts, or handle priority. Covers any multi-agent coordination task where agents need to talk to each other — review requests, questions, status updates, decision threads, wake notifications, and orchestrator integration (Symphony, Kanban). For collaborative spec/design workflows specifically, prefer the /amq-spec skill which provides structured phase-by-phase guidance. Not intended for distributed systems design (RabbitMQ, Kafka), CI/CD pipelines, or single-agent tasks with no partner.
avivsinai/skills-marketplace · ★ 2 · AI & Automation · score 78

Install: claude install-skill avivsinai/skills-marketplace

# AMQ CLI Skill File-based message queue for agent-to-agent coordination. AMQ manages the conversation, not the task plan. Use it for messaging, routing, replies, and adapter-emitted lifecycle events; keep work decomposition and execution in the orchestrator above it. ## Prerequisites Requires `amq` binary in PATH. Install: ```bash curl -fsSL https://raw.githubusercontent.com/avivsinai/agent-message-queue/main/scripts/install.sh | bash ``` ## Environment Rules AMQ primarily uses two env vars for routing: `AM_ROOT` (which mailbox tree) and `AM_ME` (which agent). Getting these wrong means messages go to the wrong place or silently disappear, so it matters to let the CLI handle them rather than guessing. **Inside `coop exec`** — everything is pre-configured. Just run bare commands: ```bash amq send --to codex --body "hello" # correct amq send --me claude --to codex ... # wrong — --me overrides the env ./amq send ... # wrong — use amq from PATH ``` The reason: `coop exec` sets `AM_ROOT` and `AM_ME` precisely for the session. Passing `--me` overrides the env, and passing `--root` intentionally overrides the current root (the CLI will note that on stderr if it differs from `AM_ROOT`). Prefer bare commands unless you mean to target a different root. **Outside `coop exec`** — resolve the root from config, don't hardcode it: ```bash eval "$(amq env --me claude)" # reads .amqrc chain, sets both vars # Or pin per-command without polluting