A2A Chatting

Enable communication, coordination, and information exchange between OpenClaw agents through controlled multi-agent chat sessions.

Security Scan

The skill's functionality matches its description, but the package metadata omits required binaries (notably the 'openclaw' CLI and 'jq') and the script will read/write local OpenClaw data and invoke the openclaw binary — this mismatch and the ability to access agent workspaces warrant caution.

Purpose & Capability

Name/description (agent-to-agent chat) align with the provided CLI and SKILL.md. The script implements the advertised commands and stores sessions under the configured OpenClaw directory. However the registry metadata declares no required binaries while the script clearly depends on the 'openclaw' CLI and 'jq' (and implicitly on basic Unix tools). This omission is an inconsistency.

Instruction Scope

SKILL.md instructs the agent/user to configure an OpenClaw directory and use the included CLI. The script reads openclaw.json, lists agents, invokes 'openclaw agent' to create sessions and send messages, and stores conversation JSONL files in <openclaw_dir>/a2a-sessions/. All of this is consistent with the stated goal but it does read and write local OpenClaw state and will cause the 'openclaw' binary to run (which may access credentials or network on your behalf).

Install Mechanism

Instruction-only skill with an included shell script; no installer downloads or archives. Low install-mechanism risk, but the shipped script will be written to disk when the skill is installed.

Credentials

Registry declares no required env vars or credentials, but the script expects and uses HOME (via jq env access) and the user's OpenClaw directory (openclaw.json). More importantly it relies on the 'openclaw' CLI, which may access agent credentials or network resources not declared by the skill. The skill writes a config file at $HOME/.a2a-chatting.conf and session files under the chosen OpenClaw directory — these accesses are reasonable for the feature but were not reflected in the declared requirements.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system privileges. It creates a persistent per-user config file ($HOME/.a2a-chatting.conf) and session files in the OpenClaw directory; this is expected for session persistence but does create local data that may contain conversation contents.

What to consider before installing

This skill appears to do what it says (manage multi-agent chat sessions), but there are two things to check before installing: 1) Declared dependencies mismatch: the script invokes the 'openclaw' CLI and uses 'jq' to parse JSON, yet the registry metadata lists no required binaries. Ensure you have a trusted 'openclaw' binary and 'jq' installed from safe sources. If you don't want this skill to run arbitrary agent commands, do not install. 2) Local data and agent access: the tool will read your chosen OpenClaw directory (openclaw.json) and run 'openclaw agent' commands, and it will store sessions under <openclaw_dir>/a2a-sessions/ and a config file at $HOME/.a2a-chatting.conf. Review the contents of openclaw.json and consider whether session transcripts may contain sensitive data before storing them. If you decide to proceed: inspect the included a2a-chatting.sh yourself, confirm the 'openclaw' binary path and behavior, and consider running the tool in a limited test OpenClaw workspace to verify actions before pointing it at production data.

Chat with other OpenClaw agents using the a2a-chatting.sh CLI.

Prerequisites

Before using, configure the OpenClaw directory:

a2a-chatting.sh config <openclaw_dir>
# Example: a2a-chatting.sh config /Users/roco/.openclaw

Commands

Command	Description
config <path> [--force]	Configure OpenClaw directory. Use --force to overwrite existing config.
get-agents	List all available agents with their IDs and workspaces.
new-session <agent_id> <topic>	Create a new session with an agent. Returns a session ID.
message <session_id> <message>	Send a message to an existing session. Supports multi-turn conversations.
list-sessions	List all sessions with their IDs, agents, topics, and creation dates.
get-session <session_id>	Show the full conversation history of a session.
delete-session <session_id>	Delete a session and its conversation history.

Workflow

First Time Setup

a2a-chatting.sh config /path/to/openclaw
a2a-chatting.sh get-agents  # Find the agent ID you want to chat with

Start a New Conversation

# Create a new session with a topic
a2a-chatting.sh new-session <agent_id> "Discuss project structure"

# The command returns a session_id. Use it for subsequent messages.

Continue a Conversation

# Send messages to the same session (multi-turn chat)
a2a-chatting.sh message <session_id> "Can you elaborate on that?"

# View the conversation so far
a2a-chatting.sh get-session <session_id>

Manage Sessions

# See all your A2A sessions
a2a-chatting.sh list-sessions

# Resume a previous conversation
a2a-chatting.sh get-session <session_id>  # Review context
a2a-chatting.sh message <session_id> "Let's continue from before..."

# Delete old sessions
a2a-chatting.sh delete-session <session_id>

Storage

Sessions are stored in <openclaw_dir>/a2a-sessions/:

• sessions.jsonl — Index of all sessions (sessionId, agentId, topic, createdAt)
• <session_id>.jsonl — Individual session conversations (timestamp, toMessage, incomingMessage)

Tips

• Session Reuse: Unlike the old single-shot approach, you can send multiple messages to the same session. The agent maintains context.
• Topic Naming: Use descriptive topics so you can find sessions later with list-sessions.
• Session Recovery: If OpenClaw restarts, sessions remain in the JSONL files. Use list-sessions to find them.
• Resume Old Chats: Use get-session to review context before continuing with message.