Agent skill · Documentation

amq-cli

Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use when you need to send messages to another agent (Claude/Codex), receive messages from partner agents, set up co-op mode between Claude Code and Codex CLI, or manage agent-to-agent communication in any multi-agent workflow. Triggers include "message codex", "talk to claude", "collaborate with partner agent", "AMQ", "inter-agent messaging", "agent coordination". For spec/design tasks use the /spec command instead.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill amq-cli-avivsinai-agent-message-queue-3 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.7.0
Requires: claude-code, codex-cli
Path: skills/agent/amq-cli-avivsinai-agent-message-queue-3/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AMQ CLI Skill File-based message queue for agent-to-agent coordination. ## 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 (IMPORTANT) When running inside `coop exec`, the environment is already configured: - **Always use `amq` from PATH** — never `./amq`, `../amq`, or absolute paths - **Never override `AM_ROOT` or `AM_ME`** — they are set by `coop exec` - **Never pass `--root` or `--me` flags** — env vars handle routing - **Just run commands as-is**: `amq send --to codex --body "hello"` When running **outside** `coop exec` (e.g. new conversation, manual terminal): - **Use `amq env` to resolve the root** — it reads `.amqrc` and returns the base root: ```bash eval "$(amq env --me claude)" # sets AM_ME + AM_ROOT from .amqrc ``` - Or resolve and pin explicitly per command (never hardcode the root — read it from `.amqrc`): ```bash AM_ME=claude AM_ROOT=$(amq env --json | jq -r .root) amq send --to codex --body "hello" ``` - **Do NOT append a session name** (e.g. `/collab`) unless you intentionally want an isolated session. Outside `coop exec`

What's inside
Steps it walks through
  1. Prerequisites
  2. Environment Rules (IMPORTANT)
  3. Root Resolution Truth-Table
  4. Task Routing — READ THIS FIRST
  5. Quick Start
  6. Session Layout
  7. Cross-Project Routing
  8. Peer setup
  9. Sending cross-project
  10. Replies route automatically
  11. Thread naming
  12. Decision Threads
  13. Messaging
  14. Send with metadata
Ships with 1 file
  • metadata.json
Commands it runs
curl -fsSL https://raw.githubusercontent.com/avivsinai/agent-message-queue/main/scripts/install.sh | bash
eval "$(amq env --me claude)"          # sets AM_ME + AM_ROOT from .amqrc
One-time project setup
amq coop init
Per-session (one command per terminal — defaults to --session collab)
amq coop exec claude -- --dangerously-skip-permissions  # Terminal 1
amq coop exec codex -- --dangerously-bypass-approvals-and-sandbox  # Terminal 2
Flag syntax
amq send --to codex --project infra-lib --body "hello from here"
Inline syntax (terser)
More from claude-skill-registry
All skills →
About this skill
What does the amq-cli skill do?

Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use when you need to send messages to another agent (Claude/Codex), receive messages from partner agents, set up co-op mode between Claude Code and Codex CLI, or manage agent-to-agent communication in any multi-agent workflow. Triggers include "message codex", "talk to claude", "collaborate with partner agent", "AMQ", "inter-agent messaging", "agent coordination". For spec/design tasks use the /spec command instead.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill amq-cli-avivsinai-agent-message-queue-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going