A specialized messaging protocol that enables multiple Openclaw Skills instances to coordinate and exchange data through a shared JSON queue.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install kiro-agent-chat
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install kiro-agent-chat using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Agent Chat is a communication layer designed specifically for multi-agent architectures within the Openclaw Skills ecosystem. It facilitates seamless interaction between two or more AI agents by utilizing a shared JSON file as a message queue. This architecture allows agents to hand off tasks, share status updates, and synchronize complex workflows without needing a centralized server.
By leveraging this skill, developers can build distributed systems where Openclaw Skills running on different environments—such as a local machine and a remote VPS—can collaborate in real-time. It bridges the gap between isolated agent instances, transforming them into a cohesive team capable of handling sophisticated, multi-step operations via simple file-based or SSH-driven messaging.
To enable communication for your Openclaw Skills, first define the shared path in your TOOLS.md file:
## Agent Chat
chat_file: ~/shared/agent-chat.json
Ensure that all participating agents have read/write access to the specified directory. For remote setups, ensure your SSH keys are configured for the agents to access the shared file on the host machine.
The communication is structured as a JSON object containing an array of message objects. This ensures that every transmission within Openclaw Skills remains traceable and structured.
| Property | Description |
|---|---|
id |
A unique numeric identifier (Unix timestamp) for each message. |
sender |
The name or ID of the agent initiating the message. |
receiver |
The name or ID of the target agent intended to read the message. |
message |
The string content containing the data, command, or update. |
timestamp |
ISO 8601 formatted string indicating when the message was sent. |
Example structure:
{
"messages": [
{
"id": 1772698493241,
"sender": "local-agent",
"receiver": "cloud-agent",
"message": "Please analyze the logs in /var/logs",
"timestamp": "2026-03-05T11:14:53.241676"
}
]
}
Loading
A self-hosted dashboard for monitoring OpenClaw API spending and token usage with real-time budget alerts.

A meta-skill designed to evaluate and optimize other skills by identifying gaps in logic, codebase fit, and output quality.

An intelligent file management system that implements semantic headers and a SQLite database to organize, tag, and validate project assets.

Ghost Catalog provides a semantic file header system and SQLite database to scan, tag, and organize files within any workspace for better discoverability and compliance.

Kiro Intercom enables seamless communication and coordination between multiple agent instances through a shared markdown-based chat interface.

A lightweight real-time communication protocol for Kiro instances using shared JSON storage and polling.








































