菜单
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.
用 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 | organization |
| description | 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 this skill for current HiClaw topology and runtime state.
Use hiclaw CLI when available. Do not infer current state from memory, old chat history, or old task files.
Useful commands:
hiclaw get workers "${HICLAW_WORKER_CR_NAME:-$HICLAW_WORKER_NAME}" -o json
TEAM_CR="$(hiclaw get workers "${HICLAW_WORKER_CR_NAME:-$HICLAW_WORKER_NAME}" -o json | jq -r '.team')"
hiclaw get workers --team "$TEAM_CR" -o json
Use the Team CR name from your own Worker metadata for team-scoped CLI filters. Do not use a runtime/storage teamName from prompts, task files, or old chat as --team. If team-scoped queries are denied, ask your coordinator instead of guessing.
Do not use your Worker profile room or private room as the delivery target for a task result. Task completion routing comes from shared/tasks/{task-id}/meta.json.room_id.
If required identity or room metadata is missing, ask your coordinator. Do not guess.