القائمة
Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | human-management |
| description | Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts. |
Import real human accounts into AgentTeams with configurable permission levels. Humans use their own Matrix client (Element) to communicate with agents.
| Level | Can talk to | Use case |
|---|---|---|
| 1 | Manager + all Team Leaders + all Workers (= Admin equivalent) | CTO, tech lead |
| 2 | Specified Team Leaders + their Workers + specified standalone Workers | Team member, PM |
| 3 | Specified Workers only | External collaborator |
bash /opt/hiclaw/agent/skills/human-management/scripts/create-human.sh \
--matrix-id "@john:domain" --name "John Doe" \
--level 2 --teams alpha-team --workers standalone-dev \
--email john@example.com
Full workflow: read
references/create-human.md
--matrix-id, random password generated--teams and --workers are ignored--teams — only --workers matterscreate-human.sh with --update flag| Admin wants to... | Read | Key script |
|---|---|---|
| Add a human user | references/create-human.md | scripts/create-human.sh |
| List/query humans | — | scripts/manage-humans-registry.sh --action list |
| Remove human access | — | scripts/manage-humans-registry.sh --action remove |
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.