manage-channels Skill
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure. Published by microsoft in amplifier-app-nanoclaw.
What is manage-channels Skill?
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure. Published by microsoft in amplifier-app-nanoclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Database workflows
- Documentation
- Data analysis
- Database workflows use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use manage-channels Skill
- Use it for database workflows.
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-nanoclaw
- Skill file: .claude/skills/manage-channels/SKILL.md
What it does
Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure.
Skill instructions
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 unknownsenderpolicy (strict | requestapproval | 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 agentgroups.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 assistantname, folder, agentprovider FROM agentgroups; SELECT id, channeltype, platformid, name, unknownsenderpolicy FROM messaginggroups; SELECT messagin
Explore related resources
Frequently asked questions
What is manage-channels?
manage-channels is a open-source AI agent skill with Copy skill directory. Wire channels to agent groups, manage isolation levels, add new channel groups. Use after adding a channel, during setup, or standalone to reconfigure.
Who is manage-channels best for?
manage-channels is best for reusing agent instructions, scripts, and references, database workflows, documentation workflows, data analysis workflows.
How do I install manage-channels?
Install or run manage-channels using Copy skill directory. Check manage-channels for the latest setup command.
Is manage-channels actively maintained?
manage-channels may need a closer maintenance check before production use.
Auto-fetched from GitHub.
