Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).
インストールする前に、エージェントに与えられる指示の中身を確認できます。
When your coordinator notifies you that your config has been updated (e.g., model switch, skill update), trigger an immediate sync:
hermes-sync
This pulls openclaw.json, SOUL.md, AGENTS.md, and skills from MinIO and re-bridges the config into ~/.hermes/ (config.yaml + .env).
Hot reload caveats:
SOUL.md on the next message — no restart needed~/.hermes/skills/ are picked up on the next message as wellconfig.yaml (model, terminal, matrix behavior) require a process restart — your coordinator handles this when neededAutomatic background sync:
The shared/ directory is automatically mirrored from MinIO at startup and every sync cycle. No manual pull is needed.
Task and project files are at:
| Local path (auto-synced) |
|---|
shared/tasks/{task-id}/ |
shared/projects/{project-id}/ |
# Read the spec (already synced locally)
cat shared/tasks/{task-id}/spec.md
# Push your results back to MinIO (push is still manual)
bash ./skills/file-sync/scripts/push-shared.sh tasks/{task-id}/ --exclude "spec.md" --exclude "base/"
The push-shared.sh script automatically detects your team and pushes to the correct MinIO path.
When to use:
push-shared.shhermes-sync to trigger an immediate pullAlways confirm to the sender after push completes.
Example workflow:
# Coordinator assigns task: "New task [st-01]. Please file-sync and read shared/tasks/st-01/spec.md"
# Run file-sync to pull latest
hermes-sync
# Read the spec
cat shared/tasks/st-01/spec.md
# ... do the work ...
# Push results
bash ./skills/file-sync/scripts/push-shared.sh tasks/st-01/ --exclude "spec.md" --exclude "base/"
# Confirm to coordinator
"Task complete. Results pushed to MinIO."
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker
日本語の概要は準備中です。原文の説明を表示しています。
Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.
日本語の概要は準備中です。原文の説明を表示しています。
将编码工作委托给 Manager 持有的 AI CLI 工具（Claude Code / Gemini CLI / qodercli）执行
日本語の概要は準備中です。原文の説明を表示しています。
Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli) on behalf of Workers. Use when a Worker sends a coding-request: message, asking Manager to run coding operations in their workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Use before sending or suppressing any Leader message to Workers, Manager, or Team Admin. Always use this skill for cross-room Matrix messages, @mention decisions, task assignment notifications, structured status reports, completion reports, blocker/revision messages, questions, requester updates, or when deciding whether a same-room reply is enough.
日本語の概要は準備中です。原文の説明を表示しています。