// 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.
Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.
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.
Use before any Worker taskflow call or assigned-task workflow, including reading task state, acknowledging a task, executing a task, tracking progress, handling blockers/questions, submitting structured results, or reporting completion. Always use this skill when the message mentions assigned task, task ID, shared/tasks, spec.md, meta.json, result.md, deliverables, BLOCKED, REVISION_NEEDED, SUCCESS, submit_task, or ack_task.
Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.
Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.
| name | file-sharing |
| description | 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. |
Use local shared paths only. Do not expose storage internals.
Use:
shared/tasks/{task-id}/shared/projects/{project-id}/ only for read-only project contextDirectory sync paths must end with /. If a directory pull fails, report the filesync result instead of creating local placeholder directories or switching to absolute paths.
Do not use in chat, task outputs, or normal reasoning:
hiclaw/hiclaw-storage/...teams/{team}/shared/.../root/hiclaw-fs/.../root/.hiclaw-worker/...taskflow(action="ack_task") and taskflow(action="submit_task") handle all task lifecycle file sync internally (pull, push, stat). Do not call filesync separately for these operations.
For shared files outside the task lifecycle (project context, reference materials), call filesync before reading:
{
"action": "pull",
"payload": {
"path": "shared/projects/{project-id}/"
}
}
To push mid-task progress or non-result files that the coordinator needs before submission:
{
"action": "push",
"payload": {
"path": "shared/tasks/{task-id}/progress/",
"exclude": ["spec.md", "base/"]
}
}
Call filesync with action="pull" for shared/tasks/{task-id}/.
Check pwd, then check the local relative path from the task message:
pwd
ls -la
ls -la shared/tasks/{task-id}/
If still missing, @mention your coordinator with the filesync outcome and the exact local path you checked:
@coordinator:domain BLOCKED: I pulled shared/tasks/{task-id}/ but cannot find shared/tasks/{task-id}/spec.md.
Do not search random container absolute paths or create the missing task directory yourself.