manage-channels

Wire messaging channels to agent groups and configure isolation levels in NanoClaw.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill manage-channels-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-channels
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/manage-channels
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill manage-channels-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Connecting Telegram, Discord, WhatsApp, or other messaging channels to the right agent groups requires manual database wiring and isolation decisions that are easy to get wrong. This Skill inspects the current configuration, guides isolation choices, and registers channel-to-agent wiring correctly. ## Core Features & Use Cases - State Assessment: Queries the central SQLite database to categorize channels as wired, configured-but-unwired, or not configured, and lists privileged users. - Channel Wiring: Registers new channels with the correct session mode (shared, agent-shared, or per-thread) and folder-based isolation, including Telegram pair-code flows for adding groups. - Rewiring & Reporting: Moves channels between agent groups, manages agent_destinations entries, and displays a readable summary of the full configuration. - Use Case: After adding a Discord bot token to your NanoClaw instance, use this Skill to wire the Discord server to an existing agent group with shared sessions, or create a fully isolated new agent. ## Quick Start Ask the assistant to wire my Telegram group to a new isolated agent and show the current channel configuration.

Frequently Asked Questions about manage-channels

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

FAQPage Schema
How do I connect a Telegram group to a NanoClaw agent?

Run the pair-telegram setup step with an intent like wire-to:<folder> or new-agent:<folder>, then post the shown pair code as @<botname> CODE in the target group. Finish by running the register step with the platform ID, folder, channel type, and session mode.

How do I check which channels are wired to which agents?

Query the central database with pnpm exec tsx scripts/q.ts data/v2.db, selecting from agent_groups, messaging_groups, and messaging_group_agents. Channels with credentials but no database rows are configured but unwired.

What isolation options exist when wiring a channel to an agent?

Three options exist: agent-shared mode puts all messages in one conversation, shared mode gives separate threads with a common workspace, and a new folder creates a fully separate agent. The choice depends on whether the same users or different people use the channel.

Can I move a channel from one agent group to another?

Yes, delete the old messaging_group_agents row and create a new one pointing to the target agent group. Existing sessions stay with the old agent, and the old agent_destinations row must be removed manually if the channel should no longer be a named target.

Why is there no main channel or admin channel concept?

Privilege in NanoClaw is user-level, not channel-level. Any user can be granted owner or admin roles via grantRole(), and unknown senders are gated per messaging group by the unknown_sender_policy setting.