菜单
Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | channel-management |
| description | Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels. |
| assign_when | Not assigned to workers — this is a manager-only capability |
Manages communication channels, admin identity recognition, trusted contacts, and primary channel configuration.
--action reset to revert to itmessage tool from a Matrix session, you MUST explicitly set channel and target — otherwise the message goes to the current Matrix room instead of the primary channelto field in primary-channel.json maps to target parameter in message tool — pass the value directly, no transformation neededhiclaw get managers -o json for runtime, then message tool or copaw channels send per finite/infinite references). Never embed @worker task assignments in admin DM replies.Read the relevant doc before executing. Do not load all of them.
| Situation | Read |
|---|---|
| Need to identify who sent a message (admin, worker, trusted contact, unknown) | references/identity-and-contacts.md |
| Add/remove trusted contacts | references/identity-and-contacts.md |
| Configure primary channel, send notifications, first-contact protocol, cross-channel escalation | references/primary-channel.md |
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.