manage-channels
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure.
Profile →npx skills add nanocoai/nanoclaw --skill manage-channels --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Manage Channels Wire messaging channels to agent groups. See `docs/isolation-model.md` for the full isolation model. Privilege is a **user-level** concept, not a channel-level one (see `src/modules/permissions/db/user-roles.ts`, `src/modules/permissions/access.ts`). There is no "main channel" / "main group" — any user can be granted `owner` or `admin` (global or scoped to an agent group) via `grantRole()`, and messages from unknown senders are gated per-messaging-group by `unknown_sender_policy` (`strict` | `request_approval` | `public`). ## Assess Current State Read the central DB (`data/v2.db`) using these canonical queries (column names match the schema, not the CLI flags — the `register` command's `--assistant-name` is stored in `agent_groups.name`). Run each via the in-tree wrapper — the host setup deliberately ships no `sqlite3` CLI: ```bash pnpm exec tsx scripts/q.ts data/v2.db "<query>" ``` ```sql SELECT id, name AS assistant_name, folder, agent_provider FROM agent_groups; SELECT id, channel_type, platform_id, name, unknown_sender_policy FROM messaging_groups; SELECT messaging_group_id, agent_group_id, engage_mode, engage_pattern, session_mode, threads, priority FROM mess
- Assess Current State
- First Channel (No Agent Groups Exist)
- Channel Defaults: The Two-Level Model
- Wiring via ncl
- Threading override (--threads)
- Mention capability
- Wire New Channel
- Isolation Question
- Register Command
- Add Channel Group
- Change Wiring
- One-Time Check: Legacy Mis-Wired WhatsApp Groups
- Show Configuration
pnpm exec tsx scripts/q.ts data/v2.db "<query>" ncl messaging-groups create --channel-type <type> --platform-id "<id>" --name "<name>" [--is-group 1] ncl wirings create --messaging-group-id <mg-id> --agent-group-id <ag-id> [--session-mode <mode>] ncl wirings update <id> --engage-mode pattern --engage-pattern '(?i)^@?<Name>\b' pnpm exec tsx setup/index.ts --step register -- \
What does the manage-channels skill do?
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure.
How do I install it?
Run `npx skills add nanocoai/nanoclaw --skill manage-channels --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.