channel-management

Configure sender identity, trusted contacts, and primary notification channels in Matrix workflows.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill channel-management-agentscope-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: channel-management
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/skills/channel-management
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill channel-management-agentscope-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents incorrect or unsafe messaging by correctly identifying who is speaking in each room, validating trusted contacts, and routing admin notifications to the right primary channel.

Core Features & Use Cases

  • Sender identity & trust resolution: Distinguishes admin, team leaders, workers, trusted contacts, and unknown senders, including the rule to silently ignore unknowns.
  • Trusted contacts governance: Adds/removes trusted contacts while enforcing strict limits to avoid sharing sensitive information or executing management operations.
  • Primary notification channel management: Sets and resets a non-Matrix primary channel (with Matrix as fallback), enforces safety constraints (e.g., cannot set primary to "matrix"), and handles first-contact language-aware prompts.
  • Cross-channel escalation routing: Coordinates how questions escalate from a blocked Matrix workflow back to the admin via the primary channel.

Quick Start

Use channel-management when your message context needs to identify the sender, verify whether they are trusted, and (if appropriate) configure or update the admin’s primary notification channel.

Frequently Asked Questions about channel-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does sender identity recognition work for enterprise IM environments?

Sender identity recognition distinguishes admins, team leaders, workers, trusted contacts, and unknown senders across room types. It enforces security by silencing unknown senders and validating primary channel updates before routing admin notifications.

How do I configure primary notification channels and prevent Matrix fallback issues?

To configure primary notification channels, set a non-Matrix primary channel while Matrix acts as a fallback. You cannot set the primary channel to "matrix" directly, ensuring proper cross-channel escalation routing for admin notifications.

What are the limitations when adding trusted contacts for management operations?

Trusted contacts governance enforces strict limits to prevent sharing sensitive information or executing management operations. You can add or remove trusted contacts, but they are restricted from accessing sensitive data or performing administrative tasks.

Why does cross-channel escalation route blocked Matrix workflows back to the admin?

Cross-channel escalation routes blocked Matrix workflows back to the admin via the primary channel to ensure questions are addressed securely. It coordinates how proactive messaging requires explicit channel and target routing to maintain access control.

Can I use channel management for first-contact onboarding with language-aware prompts?

Yes, channel management handles first-contact onboarding by providing language-aware prompts. It validates trusted contacts and applies identity management rules to ensure secure admin and worker collaboration in enterprise IM environments.

What is the best way to handle access control and identity management for matrix messaging?

The best way to handle access control for Matrix messaging is to enforce explicit channel and target routing for proactive messaging. This ensures sender identity is verified, unknown senders are silenced, and sensitive data is not disclosed to trusted contacts.