nanoclaw-gws-ea: Skill for Claude Code

.claude/skills/manage-channels/SKILL.md

manage-channels is a skill for Claude Code from taslim/nanoclaw-gws-ea. It costs 34 tokens per session (1,410 once invoked), scanned A, original, MIT.

A configuration tool for connecting messaging channels to NanoClaw agent groups. An agent group is a separate workspace or assistant configuration that can receive messages.

In plain words
What is it for?
Reviewing current channel links, adding or changing channel groups, choosing isolation settings, and configuring who may contact an agent.
Why use it?
It removes the need to edit database records by hand when changing channel connections, isolation, or access for unknown senders.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is taslim/nanoclaw-gws-ea's own configuration. It tells Claude Code how to work on nanoclaw-gws-ea itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nanoclaw-gws-ea configures →

Reuse

Borrowing it

Nothing to install: this file belongs to taslim/nanoclaw-gws-ea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/taslim/nanoclaw-gws-ea/main/.claude/skills/manage-channels/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/taslim/nanoclaw-gws-ea

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for manage-channels

README.md
[![agentmods](https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/manage-channels/github.svg)](https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/manage-channels)
Your own site
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/manage-channels"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/manage-channels/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for manage-channels

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/manage-channels"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/manage-channels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01410
Opus 5 $0.00017 $0.00705
Sonnet 5 $0.00007 $0.00282
Haiku 4.5 $0.00003 $0.00141

Measured 12d ago against content hash d6a0b37496a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

manage-channels scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/manage-channels/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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) 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:

pnpm exec tsx scripts/q.ts data/v2.db "<query>"
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, session_mode, priority FROM messaging_group_agents;
SELECT user_id, role, agent_group_id FROM user_roles ORDER BY role='owner' DESC;

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.

Read the full file on GitHub · 103 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 103 lines · 34 tokens per session scan A d6a0b37496a3

Subscribe to this mod's changes

manage-channels is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,410 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens