10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Fleet Communication Skill
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install dagangtj/fleet-commInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Multi-agent communication system for OpenClaw fleets. Enables real-time messaging between multiple OpenClaw instances running on different machines.
The skill runs a lightweight HTTP message bus on the coordinator node (default port 18800).
node fleet-comm/fleet_bus.js
FLEET_NODE_ID — This node's ID (default: 00)FLEET_BUS_URL — URL of the message bus (default: http://127.0.0.1:18800)FLEET_BUS_PORT — Port to run bus on (default: 18800)node fleet-comm/fleet_cli.js send <target_node> <message>
# Example: node fleet-comm/fleet_cli.js send 01 "start bounty scan"
node fleet-comm/fleet_cli.js broadcast <message>
node fleet-comm/fleet_cli.js read
node fleet-comm/fleet_cli.js status
00 (Mac Mini) 01 (WSL2) 02 (Windows)
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Fleet Bus │◄────────│ CLI/Poll │ │ CLI/Poll │
│ :18800 │─────────►│ │ │ │
└──────────┘ └──────────┘ └──────────┘
▲ │
└─────────────────────────────────────────┘
Tailscale Network
{
"from": "00",
"to": "01", // or "all" for broadcast
"msg": "message text",
"type": "task|info|alert|result",
"ts": 1234567890
}
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Fleet Communication Skill
Multi-agent communication system for OpenClaw fleets. Enables real-time messaging between multiple OpenClaw instances running on different machines.
## When to use
- User asks agents to communicate with each other
- Multi-machine OpenClaw setups need coordination
- Task delegation between fleet nodes
- Broadcasting announcements to all nodes
## Setup
The skill runs a lightweight HTTP message bus on the coordinator node (default port 18800).
### Start the bus (on coordinator node)
```bash
node fleet-comm/fleet_bus.js
```
### Environment
- `FLEET_NODE_ID` — This node's ID (default: `00`)
- `FLEET_BUS_URL` — URL of the message bus (default: `http://127.0.0.1:18800`)
- `FLEET_BUS_PORT` — Port to run bus on (default: `18800`)
## Commands
### Send a message to a specific node
```bash
node fleet-comm/fleet_cli.js send <target_node> <message>
# Example: node fleet-comm/fleet_cli.js send 01 "start bounty scan"
```
### Broadcast to all nodes
```bash
node fleet-comm/fleet_cli.js broadcast <message>
```
### Read messages for this node
```bash
node fleet-comm/fleet_cli.js read
```
### Check bus status
```bash
node fleet-comm/fleet_cli.js status
```
## Architecture
```
00 (Mac Mini) 01 (WSL2) 02 (Windows)
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Fleet Bus │◄────────│ CLI/Poll │ │ CLI/Poll │
│ :18800 │─────────►│ │ │ │
└──────────┘ └──────────┘ └──────────┘
▲ │
└─────────────────────────────────────────┘
Tailscale Network
```
## Message Format
```json
{
"from": "00",
"to": "01", // or "all" for broadcast
"msg": "message text",
"type": "task|info|alert|result",
"ts": 1234567890
}
```
## Free vs Pro (future)
- Free: basic messaging, broadcast, status
- Pro: encrypted messages, web dashboard, task queue, auto-discovery, message persistencegenerate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.