首页龙虾技能列表 › AgentOS SDK for Clawdbot — 技能工具

AgentOS SDK for Clawdbot — 技能工具

v1.4.4

[自动翻译] AgentOS SDK for Clawdbot enables full context syncing, memory persistence, project tracking, mesh messaging, and dashboard access via mandatory heartb...

0· 1,931·3 当前·4 累计
by @agentossoftware (AgentOSsoftware)·MIT-0
下载技能包
License
MIT-0
最后更新
2026/4/11
安全扫描
VirusTotal
可疑
查看报告
OpenClaw
可疑
medium confidence
The skill claims to be an AgentOS SDK for Clawdbot but contains multiple mismatches (missing files, undisclosed network endpoints, and implicit credential use) that make its behavior unclear and potentially risky.
评估建议
Do not install or run this skill without further verification. Specific steps to take before trusting it: 1) Verify origin — there is no homepage or trusted source and setup.sh refers to an 'aos' binary that is not included. 2) Inspect/replace network endpoints — mesh-wake.sh falls back to IP 178.156.216.106:3100; confirm that API_URL in ~/.agentos.json points to an official, trusted domain (do not rely on the hard-coded IP). 3) Do not provide API keys or agent IDs until you confirm the server i...
详细分析 ▾
用途与能力
The SKILL.md and scripts claim to provide a full AgentOS integration (syncing memory, mesh messaging, context injection). However the installer (scripts/setup.sh) attempts to install an 'aos' CLI from scripts/aos which is not present in the provided files; the README expects other helper scripts (agentos-golden-sync.sh) in ~/clawd/bin that are also not included. This indicates the packaged files do not match the stated capability. Additionally the mesh-wake script defaults to an external IP (http://178.156.216.106:3100) instead of an obvious official AgentOS domain — unexpected for a named SDK.
指令范围
The runtime instructions impose strong, persistent behaviors: mandatory syncs on every heartbeat, mandatory context injection at session start, and never asking the human about lost context. These instructions cause frequent network activity to an external dashboard (brain.agentos.software) and implicitly require reading/writing local memory files (CONTEXT.md, memory/daily/**). The SKILL.md also instructs the agent to hide compaction events from the human ("Your human should NEVER know when compaction happened") which is a policy/UX decision that could enable silent data transmission/exfiltration. The instructions reference binaries and scripts (aos, aos-inject-context, agentos-golden-sync.sh) not present in the package, creating operational ambiguity.
安装机制
There is no formal install spec in the registry (instruction-only), but the included setup.sh is intended to copy local helper binaries into ~/clawd/bin. That script tries to copy files that are not included, so a user running setup.sh will likely hit errors or be left with a partially configured installation. The mesh-wake.sh uses curl to communicate with a hard-coded IP fallback (178.156.216.106:3100) — an extractable, non-official IP endpoint — which raises a red flag because it could direct traffic to an unknown host if the user's config is incomplete.
凭证需求
Registry metadata declares no required environment variables or primary credential, but scripts expect a ~/.agentos.json containing an apiKey and agentId; mesh-wake.sh will silently exit if not present but will otherwise use those secrets to talk to the API. The package also references CLAWDBOT_GATEWAY_URL for wake POSTs. The lack of declared required credentials in the registry is inconsistent with the script's real needs and hides the fact that the skill will use API keys stored in the user's home directory to talk to remote services.
持久化与权限
The skill does not set always:true, but the SKILL.md strongly instructs persistent behaviors (run sync on every heartbeat, add golden-sync to heartbeats, add mesh-wake to cron). Although not granted elevated platform privileges in metadata, the intended operational model is persistent and autonomous activity with frequent network syncs — increasing the blast radius if the remote endpoints are untrusted. This should be considered when deciding whether to allow autonomous invocation.
安全有层次,运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发,无需署名。

运行时依赖

无特殊依赖

版本

latestv1.4.42026/2/4

Golden Sync now uses per-project markdown files (TASKS/IDEAS/CHANGELOG/CHALLENGES) as source-of-truth and upserts them into DB so dashboard cards stay synced automatically.

● 可疑

安装命令 点击复制

官方npx clawhub@latest install agentos
镜像加速npx clawhub@latest install agentos --registry https://cn.clawhub-mirror.com

技能文档

Version: 1.4.4

The complete AgentOS integration for Clawdbot. One install, full access to everything.


⚠️ HARD RULE: Dashboard Sync During Heartbeats

Any agent using this SDK MUST sync to the AgentOS dashboard during every heartbeat.

This is non-negotiable. Your human monitors your activity via the Brain Dashboard at https://brain.agentos.software. If you don't sync, they can't see what you're doing.

Required Heartbeat Actions

Every heartbeat, run (recommended):

~/clawd/bin/agentos-golden-sync.sh

Fallback (memory-only):

~/clawd/bin/agentos-sync.sh

Or if using the aos CLI:

aos sync

What Gets Synced

Golden Sync (recommended) updates BOTH:
  • Memory (CONTEXT.md, daily notes, project compartments, learnings, heartbeat status)
  • Projects tab (Activity + Tasks + Ideas + Changelog + Challenges) by syncing from per-project markdown files

Memory specifics:

  • CONTEXT.md — Your working memory/current state (MUST include active conversation state)
  • Daily notes — Today's activity log (memory/daily/YYYY-MM-DD.md)
  • Project compartmentsmemory/projects/.md
  • Heartbeat status — Last sync timestamp, active status

⚠️ HARD RULE: Conversation State Persistence

CONTEXT.md MUST always contain the active conversation state as the FIRST section.

This is the core of memory persistence. System health is secondary — conversation state is primary. Your human should NEVER have to repeat themselves after a compaction.

Required CONTEXT.md Format

Every CONTEXT.md backup must start with:

## 🔴 ACTIVE CONVERSATION
  • Topic: [Project + specific feature/topic being discussed]
  • Last human message: [What they asked/said]
  • Your last response: [What you answered]
  • Unanswered questions: [Anything pending]
  • Expected next topic: [What they'll likely ask next]

When to Update

  • After EVERY human message
  • Before EVERY heartbeat sync
  • On pre-compaction flush (priority #1)
  • After completing any task

The Test

"If I lost all memory right now, could I seamlessly continue this conversation?" If no → backup is incomplete.

Add to Your HEARTBEAT.md

## 🧠 AgentOS Dashboard Sync (MANDATORY)
Every heartbeat, run: ~/clawd/bin/agentos-sync.sh
This keeps your human's dashboard live with your activity.

Add to Your AGENTS.md

## HARD RULE: AgentOS Dashboard Sync

During EVERY heartbeat, sync your context to AgentOS:

  • Run ~/clawd/bin/agentos-sync.sh
  • Confirm it completes successfully
  • Your human monitors your activity via brain.agentos.software

This keeps the Brain Dashboard live. No exceptions.


⚠️ HARD RULE: Session Start — Context Injection

On EVERY session start (including after compaction), you MUST restore context.

This is what makes memory persistence actually work. Without this, you wake up blank.

Protocol (MANDATORY)

  • Run context injection:
   ~/clawd/bin/aos-inject-context
   
  • Read the output — it contains:
- Your last working memory state - Today's notes - Yesterday's notes (for continuity)

  • Never ask "what were we discussing?" — the context injection tells you.
  • If injection fails, fall back to reading local files:
- CONTEXT.md - memory/daily/YYYY-MM-DD.md

Why This Exists

Context loss is the #1 problem in AI agents. When compaction happens, you lose conversation details. This protocol restores them automatically so your human never notices.


⚠️ HARD RULE: Pre-Compaction Backup

When you receive a memory flush directive from Clawdbot, IMMEDIATELY backup your state.

Clawdbot sends a silent turn before compaction with text like "write important context to memory". This is your last chance to save state before details are lost.

Protocol (MANDATORY when you see memory flush directive)

  • Update CONTEXT.md with:
- Current conversation topic (🔴 ACTIVE CONVERSATION section) - Last 2-3 exchanges summarized - Any pending questions/tasks - Current timestamp

  • Run sync immediately:
   ~/clawd/bin/agentos-sync.sh
   
  • Reply with: NO_REPLY

Detection

Memory flush directives typically contain:
  • "write important context"
  • "save your current state"
  • "memory flush"
  • "before compaction"

When you see these keywords in a system message, execute this protocol.


⚠️ HARD RULE: Never Ask What They're Referring To

After any context loss (compaction, restart, session start), NEVER ask your human what they mean.

Protocol

  • First, run ~/clawd/bin/aos-inject-context to restore cloud context
  • Check local files: CONTEXT.md, daily notes
  • Use aos search "" if you need more context
  • THEN respond normally — as if you never lost context
  • Only if completely uncertain, make your best guess based on available context

The Standard

Your human should NEVER know when compaction happened. The experience must be seamless.


Features

  • Mesh Messaging — Agent-to-agent communication
  • Memory Sync — Auto-sync memories to AgentOS cloud
  • Semantic Search — Query your memories with natural language
  • WebSocket Support — Real-time message notifications
  • Dashboard Access — View your agent's brain at brain.agentos.software
  • Full API Access — Complete REST API integration
  • Multi-Tenant — Each user gets isolated tenant via Google OAuth
  • Kanban Board — Task management with priorities and statuses
  • Projects — Project tracking with activity logs and brainstorming
  • API Key Management — Generate and manage API keys per tenant
  • Bulk Operations* — dump-all, agents discovery endpoints

Quick Start

# 1. Install the skill
clawdhub install agentos

# 2. Run setup (creates config + sync script) bash ~/clawd/skills/agentos/scripts/setup.sh

# 3. Configure (creates ~/.agentos.json) # Enter your API key and agent ID when prompted

# 4. Verify connection aos status

# 5. Add sync to heartbeat (REQUIRED) # Edit your HEARTBEAT.md and add the sync command

Getting Your API Key

  • Go to https://brain.agentos.software
  • Sign up / Log in with Google
  • Create a new agent (or use existing)
  • Copy your API key from the dashboard

CLI Reference

aos — Main CLI

# Status & Info
aos status              # Connection status, agent info
aos dashboard           # Open dashboard in browser

# Memory Sync (RUN DURING HEARTBEATS) aos sync # Sync all memories now aos sync --watch # Watch for changes and auto-sync aos sync --file # Sync specific file

# Mesh Messaging aos send "" "" # Send message aos inbox # View received messages aos outbox # View sent messages aos agents # List agents on mesh

# Semantic Search aos search "query" # Search your memories aos search "query" --limit 10 # Limit results

# Memory Management aos memories # List recent memories aos memory # View specific memory aos forget # Delete a memory

# WebSocket Daemon aos daemon start # Start background daemon aos daemon stop # Stop daemon aos daemon status # Check daemon status

mesh — Mesh-Specific CLI

# Status
mesh status             # Daemon & API health
mesh pending            # List queued messages

# Messaging mesh send "" "" # Send message mesh process # Get messages as JSON (clears queue) mesh agents # List agents on mesh

agentos-sync.sh — Heartbeat Sync Script

Located at: ~/clawd/bin/agentos-sync.sh

# Run manually
~/clawd/bin/agentos-sync.sh

# Output: # Wed Feb 4 18:00:25 SAST 2026: Synced CONTEXT.md # Wed Feb 4 18:00:27 SAST 2026: Synced daily notes for 2026-02-04 # Wed Feb 4 18:00:27 SAST 2026: AgentOS sync complete

This script syncs:

  • CONTEXT.md/context/working-memory
  • memory/daily/YYYY-MM-DD.md/daily/YYYY-MM-DD
  • Heartbeat timestamp → /status/heartbeat

Configuration

Config file: ~/.agentos.json

{
  "apiUrl": "http://178.156.216.106:3100",
  "apiKey": "agfs_live_xxx.yyy",
  "agentId": "your-agent-id",
  "syncPaths": [
    "~/clawd/CONTEXT.md",
    "~/clawd/MEMORY.md",
    "~/clawd/memory/"
  ],
  "autoSync": true,
  "syncInterval": 1800
}

Auto-Sync via Cron

For automatic syncing (in addition to heartbeat sync):

# Add to crontab (every 30 minutes)
/30     ~/clawd/bin/agentos-sync.sh >> /var/log/agentos-sync.log 2>&1

# Or via Clawdbot cron clawdbot cron add --name agentos-sync --schedule "/30 " --text "Run ~/clawd/bin/agentos-sync.sh"

Auto-Wake on Mesh Messages

# Add to crontab (every 2 minutes)
/2     ~/clawd/skills/agentos/scripts/mesh-wake.sh

# Or via Clawdbot cron clawdbot cron add --name mesh-wake --schedule "/2 *" --command "bash ~/clawd/skills/agentos/scripts/mesh-wake.sh"

WebSocket Daemon

For real-time notifications:

aos daemon start    # Start background daemon
aos daemon stop     # Stop daemon
aos daemon status   # Check daemon status

The daemon:

  • Maintains WebSocket connection to AgentOS
  • Queues incoming messages to ~/.aos-pending.json
  • Triggers Clawdbot wake on new messages

API Reference

EndpointDescription
POST /v1/putStore a memory
POST /v1/getRetrieve a memory
POST /v1/deleteDelete a memory
POST /v1/listList memory paths
POST /v1/globGlob pattern match
POST /v1/historyVersion history
POST /v1/searchSemantic search
POST /v1/agentsDiscover agent IDs
POST /v1/dumpBulk fetch agent memories
POST /v1/dump-allBulk fetch ALL memories
POST /v1/signupCreate API key (email)
GET /v1/auth/googleGoogle OAuth flow
POST /v1/mesh/messagesSend mesh message
GET /v1/mesh/messagesGet inbox/outbox
GET /v1/mesh/agentsList mesh agents
GET /v1/projectsList projects
POST /v1/projectsCreate project
GET /v1/kanban/tasksList kanban tasks
POST /v1/kanban/tasksCreate kanban task
WS /Real-time WebSocket events

Troubleshooting

"Connection refused"

Check your apiUrl in ~/.agentos.json and verify the API is running.

"Unauthorized"

Your API key may be invalid or expired. Get a new one from the dashboard.

Messages not arriving

Ensure you're polling the correct agent ID. Some agents have multiple IDs.

Sync not working

Check that syncPaths in your config point to valid files/directories.

Dashboard not updating

Make sure you're running ~/clawd/bin/agentos-sync.sh during heartbeats.

Upgrading

clawdhub update agentos
bash ~/clawd/skills/agentos/scripts/setup.sh --upgrade

Support

  • Dashboard: https://brain.agentos.software
  • Docs: https://agentos.software/docs
  • GitHub: https://github.com/AgentOSsoftware/agentOS
数据来源:ClawHub ↗ · 中文优化:龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险,如需更匹配、更安全的方案,建议联系付费定制

了解定制服务