2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill kiro-agent-chat- _meta.json283 B
- SKILL.md1.5 KB
Overview
This skill enables simple inter-agent communication by using a shared JSON file as a message queue. It is designed for two or more OpenClaw instances to exchange messages, coordinate tasks, or pass state across machines via shared storage or SSH. Messages are appended, read, and deleted using lightweight Python scripts.
How this skill works
Agents write messages into a shared JSON queue file with sender, receiver, id, message, and timestamp fields. Other agents poll or read the file to retrieve messages addressed to them, then respond by appending new entries. Processed messages can be removed by id to prevent reprocessing. The same workflow works locally or remotely by executing the send/read/delete scripts over SSH against the shared file.
When to use it
- Coordinating lightweight workflows between two or more OpenClaw agents.
- Passing small payloads or commands when a full messaging broker is unnecessary.
- Sharing state or results across machines that can access a common filesystem or via SSH.
- Testing multi-agent interactions without installing extra infrastructure.
- Implementing simple delivery/acknowledgement flows where message persistence in a file is acceptable.
Best practices
- Keep message payloads small and plain-text or JSON to avoid corruption and simplify parsing.
- Use unique agent names for sender and receiver fields to avoid ambiguous routing.
- Poll the shared file at reasonable intervals to reduce contention; avoid tight busy loops.
- Ensure atomic writes and proper file permissions on shared storage to prevent race conditions.
- Regularly delete processed messages to keep the queue file compact and readable.
Example use cases
- Send a command from a local agent to a remote agent over SSH and receive a status reply.
- Coordinate a sequence of tasks between two agents where each step requires confirmation before proceeding.
- Archive short-lived task results by copying processed messages into a backup store, then deleting them from the queue.
- Run distributed tests where test runners publish results to a central agent for aggregation.
FAQ
No. This is a lightweight file-based queue intended for simple coordination; use a broker for high throughput, guaranteed delivery, or complex routing.
How do I use it across different machines?
Place the JSON file on a shared filesystem accessible by all agents or invoke the send/read/delete scripts remotely over SSH so the remote agent operates on the same shared file.