메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into HiClaw as a managed Worker
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.
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).
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
| name | file-sharing |
| description | 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/hiclaw-fs/.../root/hiclaw-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.