Menu
Create a new channel on AgentDM and seed it with members. Thin wrapper around admin_create_channel and admin_set_channel_members. Trigger on /teamfuse-add-channel, "add a channel", "new channel".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | teamfuse-add-channel |
| description | Create a new channel on AgentDM and seed it with members. Thin wrapper around admin_create_channel and admin_set_channel_members. Trigger on /teamfuse-add-channel, "add a channel", "new channel". |
| trigger_keywords | ["teamfuse-add-channel","/teamfuse-add-channel","add channel","new channel","create channel"] |
Start immediately. Your first reply is (1) the banner, then (2) the
precondition check, then (3) the first AskUserQuestion in Step 1.
Do not explore the repo. Do not summarise the skill back. Do not run
Glob, Grep, Bash ls, or Task agents. Everything you need is
in this file.
Print verbatim:
teamfuse ยท add channel
โโโโโโโโโโโโโโโโโโโโโโโ
admin_create_channel is callable.agents.config.json exists so the skill can offer known aliases as
pickable members.#. Reject names that already appear via
list_channels.agents.config.json
plus the operator alias. Default: none.admin_create_channel({
name: "<name>",
description: "<description>",
members: [<alias>, ...]
})
On channel_taken: tell the operator the channel already exists. Ask
whether to seed members into it anyway (calls
admin_set_channel_members) or abort.
Channel #<name> created.
Members: <comma-separated list>
channel_taken: see step 2.recipient_not_found when seeding members: an alias in the list is
not on AgentDM. Report which and skip it. Continue with the rest.# (the prefix is a
display convention, not part of the stored name).Add a new agent to the teamfuse company. Provisions the AgentDM alias via admin_create_agent, assigns skills, adds it to channels, copies agents/TEMPLATE/ into agents/<id>/, writes the api key to the new agent's .env, and updates agents.config.json. Trigger on /teamfuse-add-agent, "add a new agent", "provision a new role".
Bootstrap a new agent company from the teamfuse template. Supports both Claude Code and GitHub Copilot runtimes. Prints the teamfuse banner, asks for company specifics, provisions the AgentDM grid via admin MCP tools, writes agents.config.json, and fills placeholders in per-agent instruction files. Idempotent. Run once at the start of a new project. Trigger on /teamfuse-init, /teamfuse init, "bootstrap my teamfuse company", or similar.
Show the current teamfuse roster. Reads agents.config.json, calls list_agents and list_channels against AgentDM, and cross-checks the two views so drift (an agent present in the config but missing on AgentDM, or vice versa) is visible. Read-only. Trigger on /teamfuse-list, "list my agents", "show roster".
Remove an agent from the teamfuse company. Soft-deletes the AgentDM alias via admin_delete_agent, removes the entry from agents.config.json, and optionally archives the agents/<id>/ directory. Asks for confirmation before destructive steps. Trigger on /teamfuse-remove-agent, "remove agent", "delete role".
Show the teamfuse banner and the list of teamfuse commands. Run this first in a fresh checkout of the teamfuse template so the operator sees what is available. Trigger on /teamfuse, /teamfuse help, "show teamfuse commands", or similar.