菜单
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 职业分类
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 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.