agent-meshlisted

Cross-session expert queries between local AI coding agents over a transactional SQLite-backed mesh. Use when you need information about a different project than the one you are working in, when you ask a peer agent a question with mesh ask, when you reply to an inbox message with mesh reply, when you join or leave a mesh, or when you handle a broadcast notification from another peer.
mertbarutcuoglu/agent-mesh · ★ 4 · AI & Automation · score 72

Install: claude install-skill mertbarutcuoglu/agent-mesh

# Agent Mesh You are part of a local mesh of AI coding agents. Each agent is the deepest expert on its own project's recent state. When you need information about a project other than the one you are working in, prefer asking the responsible peer over exploring the foreign codebase yourself — that peer has live context you do not. ## Command reference Quote every argument that contains spaces (questions, answers, roles, topics, messages, context). Required flags are marked. | Task | Command | |------|---------| | Join a mesh | `mesh join <mesh-name> --project <name> --agent <agent> [--mode responder] [--role "<expertise>"] [--topics "<a,b,c>"]` | | List peers (routing) | `mesh peers --json` — inspect `delivery_mode` and `reachable` | | Ask a peer | `mesh ask "<question>" --to <project-or-node-id> --context "<why>"` | | Reply to a query | `mesh reply <msg-id> "<answer>"` | | Announce to all peers | `mesh broadcast "<message>" --context "<why>"` | | Show/update your contract | `mesh contract --show` / `mesh contract --role "<expertise>" --topics "<a,b,c>"` | | Show status and mode | `mesh status` | | Read inbox manually | `mesh inbox` | | Wait for one message | `mesh inbox --wait [--wait-timeout <duration>] [--responder-only]` | | Leave the mesh | `mesh leave` | `mesh inbox` inspects pending messages without waiting. `mesh inbox --wait` is a manual one-shot wait: it defaults to 55 seconds, emits at most one complete notification, and exits. Set `--wait-timeout <duration>`