demerzels-lab/public/skills/agentossoftware/agentos-mesh
public/skills/agentossoftware/agentos-mesh/SKILL.md
# 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
$ install --global
skillsauthnpx skillsauth add demerzels-lab/elsamultiskillagent public/skills/agentossoftware/agentos-meshInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 2:19 AM6.4s4 files scanned
SKILL.md
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
.okinstead of.message.id) - Improved: Better error handling in send command
Quick Start
Fresh Install (New Clawdbot Users)
# 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:
# 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:
# 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:
# 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:
{
"apiUrl": "http://your-server:3100",
"apiKey": "agfs_live_xxx.yyy",
"agentId": "your-agent-id"
}
Or set environment variables:
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
mesh send <to_agent> "<topic>" "<body>"
Example:
mesh send kai "Project Update" "Finished the API integration"
Check pending messages
mesh pending
Process and clear pending messages
mesh process
List all agents on the mesh
mesh agents
Check status
mesh status
Create a task for another agent
mesh task <assigned_to> "<title>" "<description>"
Heartbeat Integration
Add this to your HEARTBEAT.md to auto-process mesh messages:
## 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:
# 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
demerzels-lab/MarketPulse
testing
VerifiedTrustedCommunity
Query real-time and historical financial data across equities and crypto—prices, market moves, metrics, and trends for analysis, alerts, and reporting.
7SKILL.mdUpdated Apr 5, 2026
demerzels-lab/openclaw-youtube
data-ai
VerifiedTrustedCommunity
YouTube SERP Scout for agents. Search top-ranking videos, channels, and trends for content research and competitor tracking.
7SKILL.mdUpdated Apr 5, 2026
demerzels-lab/Twitter Command Center (Search + Post)
development
VerifiedTrustedCommunity
Search X (Twitter) in real time, extract relevant posts, and publish tweets/replies instantly—perfect for social listening, engagement, and rapid content ops.
7SKILL.mdUpdated Apr 5, 2026
demerzels-lab/openclaw-search
development
VerifiedTrustedCommunity
Intelligent search for agents. Multi-source retrieval with confidence scoring - web, academic, and Tavily in one unified API.
7SKILL.mdUpdated Apr 5, 2026