メニュー
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 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.
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.
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.
Use when executing a task (progress logging, plan updates), when resuming a task after session reset, or when managing task history. Covers progress log format, task-history.json, and resume flow.
| 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:
hiclaw/hiclaw-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.