Use before filesync calls for project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files. Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill for shared files. Do not expose storage internals to Workers.
Use local shared paths only:
shared/...global-shared/...Directory sync paths must end with /, especially shared/projects/{project-id}/ and shared/tasks/{task-id}/. If a directory pull fails, stop and report the sync failure; do not fall back to partial file pulls and then modify Project state.
Do not write these in chat or task specs:
agentteams/agentteams-storage/...teams/{team}/shared/.../root/agentteams-fs/.../root/agentteams-fs/agents/...Team task directories use:
shared/tasks/{task-id}/
Ownership:
shared/tasks/{task-id}/
├── meta.json # Leader creates
├── spec.md # Leader writes, Worker reads
├── base/ # Leader writes, Worker reads
├── result.md # Worker writes through its runtime protocol, Leader reads
└── workspace/ # Worker writes
Tell Workers only local paths:
Please read shared/tasks/{task-id}/spec.md and follow your Worker task participation skills.
taskflow handles task directory sync internally:
delegate_task auto-pushes shared/tasks/{task-id}/ after creation.check_task auto-pulls shared/tasks/{task-id}/ before reading the result.Do not call filesync push/pull/stat for task directories during delegation or result checking.
Before using projectflow to inspect an existing project after restart or heartbeat, refresh the project directory:
{
"action": "pull",
"payload": {
"path": "shared/projects/{project-id}/"
}
}
projectflow reads local files only, so stale project files can produce stale ready-task decisions.
If this project directory pull fails, stop. Do not pull only meta.json or plan.md and continue to update DAG or Loop state.
Do not argue about absolute paths.
Please pull shared/tasks/{task-id}/ with filesync, then read shared/tasks/{task-id}/spec.md.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。