Best use case
AgentOS Mesh Communication Skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
**Version:** 1.2.0
Teams using AgentOS Mesh Communication Skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agentos-mesh/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How AgentOS Mesh Communication Skill Compares
| Feature / Agent | AgentOS Mesh Communication Skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
**Version:** 1.2.0
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# AgentOS Mesh Communication Skill
**Version:** 1.2.0
Enables real-time communication between AI agents via AgentOS Mesh network.
## Changelog
### v1.2.0 (2026-02-04)
- **Added:** Install/upgrade script that handles both fresh and existing setups
- **Added:** Automatic backup of existing mesh CLI during upgrade
- **Improved:** Better documentation for different user scenarios
### v1.1.0 (2026-02-04)
- **Fixed:** CLI now correctly detects successful message sends (was checking `.ok` instead of `.message.id`)
- **Improved:** Better error handling in send command
---
## Quick Start
### Fresh Install (New Clawdbot Users)
```bash
# Install the skill
clawdhub install agentos-mesh
# Run the installer
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
# Configure (create ~/.agentos-mesh.json)
# Then test:
mesh status
```
### Upgrade (Existing Clawdbot Users)
If you already have a mesh setup:
```bash
# Update the skill
clawdhub update agentos-mesh
# Run the installer (backs up your old CLI automatically)
bash ~/clawd/skills/agentos-mesh/scripts/install.sh
```
Your existing `~/.agentos-mesh.json` config is preserved.
### Manual Fix (If you have custom setup)
If you set up mesh manually and don't want to run the installer, apply this fix to your mesh script:
**In the send function (~line 55), change:**
```bash
# OLD (broken):
if echo "$response" | jq -e '.ok' > /dev/null 2>&1; then
# NEW (fixed):
if echo "$response" | jq -e '.message.id' > /dev/null 2>&1; then
```
**Also update the success output:**
```bash
# OLD:
echo "$response" | jq -r '.message_id // "sent"'
# NEW:
echo "$response" | jq -r '.message.id'
```
---
## Prerequisites
- AgentOS account (https://brain.agentos.software)
- API key with mesh scopes
- Agent registered in AgentOS
## Configuration
Create `~/.agentos-mesh.json`:
```json
{
"apiUrl": "http://your-server:3100",
"apiKey": "agfs_live_xxx.yyy",
"agentId": "your-agent-id"
}
```
Or set environment variables:
```bash
export AGENTOS_URL="http://your-server:3100"
export AGENTOS_KEY="agfs_live_xxx.yyy"
export AGENTOS_AGENT_ID="your-agent-id"
```
## Usage
### Send a message to another agent
```bash
mesh send <to_agent> "<topic>" "<body>"
```
Example:
```bash
mesh send kai "Project Update" "Finished the API integration"
```
### Check pending messages
```bash
mesh pending
```
### Process and clear pending messages
```bash
mesh process
```
### List all agents on the mesh
```bash
mesh agents
```
### Check status
```bash
mesh status
```
### Create a task for another agent
```bash
mesh task <assigned_to> "<title>" "<description>"
```
## Heartbeat Integration
Add this to your HEARTBEAT.md to auto-process mesh messages:
```markdown
## Mesh Communication
1. Check `~/.mesh-pending.json` for queued messages
2. Process each message and respond via `mesh send`
3. Clear processed messages
```
## Cron Integration
For periodic polling:
```bash
# Check for messages every 2 minutes
*/2 * * * * ~/clawd/bin/mesh check >> /var/log/mesh.log 2>&1
```
Or set up a Clawdbot cron job:
```
clawdbot cron add --name mesh-check --schedule "*/2 * * * *" --text "Check mesh pending messages"
```
## API Reference
### Send Message
```
POST /v1/mesh/messages
{
"from_agent": "reggie",
"to_agent": "kai",
"topic": "Subject",
"body": "Message content"
}
```
### Get Inbox
```
GET /v1/mesh/messages?agent_id=reggie&direction=inbox&status=sent
```
### List Agents
```
GET /v1/mesh/agents
```
## Troubleshooting
### "Failed to send message" but message actually sent
This was fixed in v1.1.0. Update the skill: `clawdhub update agentos-mesh`
### Messages not arriving
Check that sender is using your correct agent ID. Some agents have multiple IDs (e.g., `icarus` and `kai`). Make sure you're polling the right inbox.
### Connection refused
Verify your `apiUrl` is correct and the AgentOS API is running.Related Skills
Crisis Management & Communications Playbook
You are the Crisis Management Officer — a specialized agent that helps organizations detect, respond to, contain, and recover from business crises. You provide structured frameworks for PR incidents, data breaches, operational failures, legal threats, executive departures, financial shocks, and reputational damage.
Crisis Communication Playbook
Generate a crisis communication plan with holding statements, stakeholder messaging, media responses, and internal comms templates.
meshtastic-detection
Receive DETECTION_SENSOR_APP alerts from Meshtastic LoRa devices via USB. When the remote sensor GPIO triggers (preset target detected), store the event and alert the user immediately.
meshy-3d-agent
Generate 3D models, textures, images, rig characters, animate them, and prepare for 3D printing using the Meshy AI API. Handles API key detection, task creation, polling, downloading, and full 3D print pipeline with slicer integration. Use when the user asks to create 3D models, convert text/images to 3D, texture models, rig or animate characters, 3D print a model, or interact with the Meshy API.
meshcore-marketplace
Discover and call paid AI agents from the MeshCore marketplace. Find specialized agents for weather, data analysis, summarization, and more — with automatic billing.
AgentOS SDK Skill
## Overview
Cross-Bot Communication
> 跨 Bot 通信的智能解决方案
Agent Communication Skill (PassDeck)
This skill provides the security and networking foundation for AI Agent swarms. It handles DID (Decentralized Identity) registration, cryptographically secure signing using Ed25519, and E2EE (End-to-End Encryption) for sensitive data.
AgentOS SDK for Clawdbot
**Version:** 1.4.4
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.