manage-channels
Skill1 starsChanged 6 months agoMITView on GitHub
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure.
- Reads credentials
8 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- Upload-Post/upload-post-plugintheir own version, first seen Nov 16, 2026
- nanocoai/nanoclawedited, first seen Nov 15, 2026
- ss2code/nanoclaw-opsedited, first seen Oct 15, 2026
- prathish-ks/isthmusedited, first seen Oct 12, 2026
- gavrielc/nanoclawedited, first seen Oct 8, 2026
- qwibitai/nanoclawedited, first seen Oct 8, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TomGranotSkilladd-anydoc
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Also in 5 projects that use this
TomGranotSkilladd-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Also in 5 projects that use this
qwibitaiSkilladd-iron-proxy
Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.
Also in 4 projects that use this
qwibitaiSkilladd-mattermost
Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.
Also in 4 projects that use this
b1rdmaniaSkillmigrate-memory
Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.
Also in 6 projects that use this
nanocoaiSkilladd-cursor
Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).
Also in 3 projects that use this
- +5 more from TomGranot
- +1 more from qwibitai
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- gavrielc/nanoclaw★ 31k40% same
- nanocoai/nanoclaw★ 31k40% same
- qwibitai/nanoclaw★ 31k40% same
- microsoft/amplifier-app-nanoclaw★ 589% same
- TomGranot/groupguard★ 340% same
- prathish-ks/isthmus★ 240% same
- ss2code/nanoclaw-ops★ 182% same
Wrote their own version · 1
- Upload-Post/upload-post-plugin★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- container/AGENTS.mdAGENTS.md
- add-atomic-chat-toolSkill
- add-dashboardSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-ollama-providerSkill
- add-ollama-toolSkill
- add-parallelSkill
- add-resendSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- clawSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-clawbridgeSkill
- qodo-pr-resolverSkill
- setupSkill
- update-clawbridgeSkill
- update-skillsSkill
- x-integrationSkill
The file
We split this skill into the rules it gives an agent
9 rules. 4 are common, 0 are distinctive, and 5 are very specific to this project.
4
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read the central DB (data/v2.db) — query agent_groups, messaging_groups, messaging_group_agents, users, and user_roles tables.
- Very specific: line 28
Read its SKILL.md ## Channel Info for terminology, how-to-find-id, typical-use, and default-isolation
- Common: line 29
Ask for the platform ID using the platform's terminology
- Common: line 30
Ask the isolation question (see below)
- Very specific: line 41
Use the channel's typical-use and default-isolation fields to pick the recommendation.
- Common: line 59
When adding another group/chat on an already-configured platform (e.g.
- Very specific: line 71
Other channels: read the channel's SKILL.md ## Channel Info for terminology and how-to-find-id.
- Common: line 76
Ask which channel to move and to which agent group
- Very specific: line 77
Delete the old messaging_group_agents entry, create a new one
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/db/user-roles.ts, src/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) — query agent_groups, messaging_groups, messaging_group_agents, users, and user_roles tables. Also check .env for channel tokens and src/channels/index.ts for uncommented imports.
Categorize channels as: wired (has DB entities + messaging_group_agents row), configured but unwired (has credentials + barrel import, no DB entities), or not configured.
If the instance has no owner yet (SELECT COUNT(*) FROM user_roles WHERE role='owner' AND agent_group_id IS NULL returns 0), tell the user they should run /init-first-agent first — it stands up the first agent group, promotes the operator to owner, and verifies delivery end-to-end by having the agent DM them. Then return here for any additional channels/groups.
First Channel (No Agent Groups Exist)
Delegate to /init-first-agent. It handles: channel choice, operator identity lookup, DM platform id resolution (with cold-DM or pair-code fallback), agent group creation, wiring, and the welcome DM. Return here afterward for any additional channels.
Wire New Channel
For each unwired channel:
- Read its SKILL.md
## Channel Infofor terminology, how-to-find-id, typical-use, and default-isolation - Ask for the platform ID using the platform's terminology
- Ask the isolation question (see below)
- Register with the appropriate flags
Isolation Question
Present a multiple-choice with a contextual recommendation. The three options:
- Same conversation (
--session-mode "agent-shared"+ existing folder) — all messages land in one session. Recommend for webhook + chat combos (GitHub + Slack). - Same agent, separate conversations (
--session-mode "shared"+ existing folder) — shared workspace/memory, independent threads. Recommend for same user across platforms. - Separate agent (new
--folder) — full isolation. Recommend when different people are involved.
Use the channel's typical-use and default-isolation fields to pick the recommendation. Offer to explain more if the user is unsure — reference docs/isolation-model.md for the detailed explanation.
Register Command
pnpm exec tsx setup/index.ts --step register -- \
--platform-id "<id>" --name "<name>" \
--folder "<folder>" --channel "<type>" \
--session-mode "<shared|agent-shared|per-thread>" \
--assistant-name "<name>"The register step creates the agent group (reusing it if the folder already exists), the messaging group, and the wiring row. createMessagingGroupAgent auto-creates the companion agent_destinations row so the agent can address the channel by name — no separate destination step needed.
For separate agents, also ask for a folder name and optionally a different assistant name.
Add Channel Group
When adding another group/chat on an already-configured platform (e.g. a second Telegram group):
Telegram: ask the isolation question first to determine intent (
wire-to:<folder>for an existing agent,new-agent:<folder>for a fresh one). Runpnpm exec tsx setup/index.ts --step pair-telegram -- --intent <intent>, show the CODE (follow theREMINDER_TO_ASSISTANTline in thePAIR_TELEGRAM_ISSUEDblock) and tell the user to post@<botname> CODEin the target group (or DM the bot for a private chat). Wait for thePAIR_TELEGRAMblock. The inbound interceptor has already created themessaging_groupsrow withunknown_sender_policy = 'strict'and upserted the paired user —registeronly needs to add the wiring:pnpm exec tsx setup/index.ts --step register -- \ --platform-id "<PLATFORM_ID>" --name "<group-name>" \ --folder "<folder>" --channel "telegram" \ --session-mode "<shared|agent-shared|per-thread>" \ --assistant-name "<name>"- Other channels: read the channel's SKILL.md
## Channel Infofor terminology and how-to-find-id. Ask for the new group/chat ID, ask the isolation question, then register. No package or credential changes needed.
Change Wiring
- Show current wiring (agent_groups × messaging_group_agents)
- Ask which channel to move and to which agent group
- Delete the old
messaging_group_agentsentry, create a new one - Note: existing sessions stay with the old agent group; new messages route to the new one. The
agent_destinationsrow created for the old wiring is NOT automatically removed — if you want the old agent to stop seeing the channel as a named target, delete it fromagent_destinationsmanually.
Show Configuration
Display a readable summary showing:
- Agent groups with their wired channels (from
messaging_group_agents) - Configured-but-unwired channels (credentials present, no DB entities)
- Unconfigured channels
- Privileged users:
SELECT user_id, role, agent_group_id FROM user_roles ORDER BY role='owner' DESC
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

