Channel Management
DevOps & Securitychannel-managementChannel Management is an Agent Skill for devops & security published in the agentscope-ai/AgentTeams repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/agentscope-ai/AgentTeams/blob/HEAD/manager/agent/skills/channel-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/channel-management, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Channel Management
Manages communication channels, admin identity recognition, trusted contacts, and primary channel configuration.
Gotchas
- Primary channel cannot be set to "matrix" — Matrix DM is the default fallback. Use
--action resetto revert to it - Unknown senders in group rooms must be silently ignored — no response at all, until admin explicitly approves them as trusted contacts
- Trusted contacts must never receive sensitive info — no API keys, tokens, passwords, Worker credentials, or internal config. No management operations either
- When calling
messagetool from a Matrix session, you MUST explicitly setchannelandtarget— otherwise the message goes to the current Matrix room instead of the primary channel tofield in primary-channel.json maps totargetparameter inmessagetool — pass the value directly, no transformation needed- First-contact protocol: always ask in admin's language — match the language they used in their message
- Task dispatch must go to Worker Room, not admin DM — when assigning tasks to Workers, use the task-management skill's send protocol (runtime-aware:
hiclaw get managers -o jsonfor runtime, then message tool orcopaw channels sendper finite/infinite references). Never embed @worker task assignments in admin DM replies.
Operation Reference
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 |