メニュー
Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into HiClaw as a managed Worker
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.
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.
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.
SOC 職業分類に基づく
| name | team-management |
| description | Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader. |
A Team consists of 1 Team Leader + N Workers. The Team Leader is a special Worker with management skills that handles task decomposition and assignment within the team. Manager delegates tasks to Team Leaders, not directly to team workers.
# 1. Create team via hiclaw CLI
hiclaw create team \
--name <TEAM_NAME> \
--leader-name <LEADER_NAME> \
--leader-model <MODEL> \
--workers <w1>,<w2>
# 2. @mention the Leader in Leader Room to assign task
After creation, the Leader is online in the Leader Room (Manager + Global Admin + Leader). @mention the Leader there to delegate the task — the Leader will decompose it and coordinate with team workers in the Team Room.
Full workflow: read
references/create-team.md
If admin asks for CPU or memory requests/limits, use a YAML Team manifest with leader.resources and/or workers[].resources, then apply it with hiclaw apply -f. The simple hiclaw create team / hiclaw update team flags do not expose resource tuning. Changing member resources recreates the affected member container, so confirm the team is not mid-task.
--team-admin not specified--delegated-to-team — so heartbeat knows to check with Leader, not workersruntime: copaw for all team members — omit runtime from team creation| Admin wants to... | Read | Command |
|---|---|---|
| Create a new team | references/create-team.md | hiclaw create team |
| Understand team lifecycle | references/team-lifecycle.md | — |
| Delegate task to team | references/team-task-delegation.md | — |
| Add/remove worker from team | references/team-lifecycle.md | hiclaw get team |
| Delete a team's containers | references/team-lifecycle.md | scripts/lifecycle-worker.sh (per worker) |