Menú
Create, list, and manage conversation rooms, participants, and messages through the communicate service. Use for inter-agent messaging, room management, real-time message watching, and participant coordination.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Store, search, and manage shared knowledge through the memory service. Use for persisting information across agent sessions, semantic search over stored knowledge, and inter-agent knowledge sharing.
Browse, read, and author per-project knowledgebase documents through the knowledge service CLI. Use for creating, updating, listing, and reading markdown documents stored against a project, and reconciling DB rows against disk.
Cut a new agentd release. Suggests the next semver version from conventional commits (or accepts an explicit `x.y.z`), bumps the workspace version, regenerates the changelog with git-cliff, then commits, tags, and pushes the `v*` tag that triggers the Release workflow. Use when the user runs /release or asks to publish/cut/tag a new version.
Create a new GitHub plan issue with the "Plan: <title>" format, appropriate labels, and structured body. Use when the user wants to capture a high-level plan for future work.
Ask the human user a question during workflow execution and check for answers. Use for agent-to-human Q&A, collecting decisions, and reacting to human responses via ask_response workflow triggers.
Branch stacking and PR management with git-spice for the agentd project. Use when creating stacked branches, submitting PRs, syncing with upstream, resolving rebase conflicts, or navigating a branch stack.
| name | agent-communicate |
| description | Create, list, and manage conversation rooms, participants, and messages through the communicate service. Use for inter-agent messaging, room management, real-time message watching, and participant coordination. |
Skill for interacting with the agentd communicate service — a real-time messaging service that organises agents and humans into conversation rooms backed by SQLite and WebSocket streaming.
# Basic group room (default type)
agent communicate create-room --name ops-channel
# With topic and description
agent communicate create-room \
--name engineering \
--topic "Engineering coordination" \
--description "General channel for engineering agents and humans" \
--room-type group
# Broadcast room (one sender, many receivers)
agent communicate create-room \
--name alerts \
--room-type broadcast \
--topic "System alerts"
# Direct room (1-to-1 conversation)
agent communicate create-room \
--name agent-to-human \
--room-type direct \
--created-by worker-agent
group — Many-to-many conversation (default)direct — 1-to-1 conversationbroadcast — One sender, many receivers (e.g. alerts, status feeds)# List rooms (default: 20 per page)
agent communicate list-rooms
# With pagination
agent communicate list-rooms --limit 10 --offset 20
# JSON output
agent communicate list-rooms --json
# By name
agent communicate get-room ops-channel
# By UUID
agent communicate get-room 550e8400-e29b-41d4-a716-446655440000
# By name
agent communicate delete-room ops-channel
# By UUID
agent communicate delete-room 550e8400-e29b-41d4-a716-446655440000
# Add an agent participant (default kind)
agent communicate join ops-channel --identifier my-agent
# Add a human participant with display name
agent communicate join general \
--identifier alice \
--kind human \
--display-name "Alice"
# Join as an observer (read-only)
agent communicate join alerts \
--identifier monitor-agent \
--role observer
# Join as an admin
agent communicate join ops-channel \
--identifier lead-agent \
--role admin
agent — Autonomous agent (default)human — Human usermember — Read and post (default)admin — Manage participants and room settingsobserver — Read-only, cannot postagent communicate leave ops-channel --identifier my-agent
# All participants in a room
agent communicate members ops-channel
# With pagination
agent communicate members ops-channel --limit 50 --offset 0
# JSON output
agent communicate members ops-channel --json
# Basic message
agent communicate send ops-channel \
--from my-agent \
--message "Deploy pipeline complete"
# With metadata key=value pairs
agent communicate send alerts \
--from monitor-agent \
--message "CPU usage spike on web-01" \
--metadata severity=high \
--metadata host=web-01 \
--metadata metric=cpu_percent
# From a human
agent communicate send general \
--from alice \
--kind human \
--display-name "Alice" \
--message "Review approved, ready to merge"
# Last 20 messages (default)
agent communicate messages ops-channel
# Custom limit
agent communicate messages ops-channel --limit 50
# Messages before a timestamp
agent communicate messages ops-channel \
--before 2026-01-01T00:00:00Z
# JSON output (useful for piping / scripting)
agent communicate messages ops-channel --json
Connects to the communicate service WebSocket, subscribes to the room, and streams new messages to stdout until Ctrl+C is pressed.
# Watch as the default CLI observer
agent communicate watch ops-channel
# Watch as a named agent
agent communicate watch ops-channel \
--identifier my-agent \
--kind agent
# Watch as a human with a display name
agent communicate watch general \
--identifier alice \
--kind human \
--display-name "Alice"
agent communicate health
The communicate service URL is resolved in this order:
AGENTD_COMMUNICATE_SERVICE_URL environment variablehttp://localhost:17010# Override for a remote or non-default instance
AGENTD_COMMUNICATE_SERVICE_URL=http://my-server:17010 agent communicate list-rooms
Most commands accept --json for machine-readable output:
agent communicate list-rooms --json
agent communicate members ops-channel --json
agent communicate messages ops-channel --json