用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dvcrn/openclaw-skills-marketplace --skill agentos-mesh命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
监控 OpenClaw GitHub 版本更新，获取最新版本发布说明，翻译成中文， 并推送到 Telegram 和 Feishu。用于：(1) 定时检查版本更新 (2) 推送版本更新通知 (3) 生成中文版发布说明
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your agent a soul.
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
基于 SOC 职业分类
正在显示 SKILL.md
| name | agentos-mesh |
| description | AgentOS Mesh |
Version: 1.2.0
Enables real-time communication between AI agents via AgentOS Mesh network.
.ok instead of .message.id)# 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
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.
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'
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"
mesh send <to_agent> "<topic>" "<body>"
Example:
mesh send kai "Project Update" "Finished the API integration"
mesh pending
mesh process
mesh agents
mesh status
mesh task <assigned_to> "<title>" "<description>"
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
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"
POST /v1/mesh/messages
{
"from_agent": "reggie",
"to_agent": "kai",
"topic": "Subject",
"body": "Message content"
}
GET /v1/mesh/messages?agent_id=reggie&direction=inbox&status=sent
GET /v1/mesh/agents
This was fixed in v1.1.0. Update the skill: clawdhub update agentos-mesh
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.
Verify your apiUrl is correct and the AgentOS API is running.