菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 TEAMS.md Communication Contract needs detailed routing: Channel / Room Selection Protocol, Requester Report Delivery Protocol, or Message Tool Protocol. It resolves current session vs Team Room vs assignment room vs requester reply_route vs external channel, and explains when to use the message MCP tool. Do not use it to choose Quick Task or Project Work, create rooms, delegate tasks, check results, or accept project state.
Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries.
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
Use only after Project Work mode is selected, before TeamHarness projectflow calls, project DAG or Loop planning, ready-node resolution, iteration recording, project files, result acceptance, or project progress updates.
Use only after Project Work mode is selected, when a TeamHarness Leader delegates ready project nodes, writes task specs, checks Worker results, and routes completion or blocker messages.
| 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-fs/agents/...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.