channels-setup — Claude Code skill: connect your agent to Slack
A skill to build your first CopilotKit Channels agent and connect it to Slack or Microsoft Teams. Walks through the entire path: from project setup to a working agent that replies to mentions in chat.
npx skills add CopilotKit/CopilotKit --skill channels-setup -a claude-codeWhat channels-setup does
channels-setup runs an interactive graph that guides you through every step. It inspects or scaffolds your project, builds the AG-UI agent, creates a managed Channel via the CopilotKit CLI, and starts the long-running host. Once it's done, your agent is ready to answer mentions in Slack or Teams.
Everything happens through one command: npx --yes copilotkit@latest onboard start. The skill itself doesn't contain written steps — it starts a graph that asks its own questions and prevents you from skipping or redoing parts. That matters: manual setup often looks complete but doesn't work.
The skill runs on the CopilotKit CLI and may ask for a session token when needed. If the command fails, the skill stops and shows the error — don't try to improvise the workflow.
What it helps with
- connect an agent to Slack or Teams from scratch
- set up your first CopilotKit Channels agent
- start a long-running host for your chat bot
- verify your agent replies to channel mentions
Example prompts for the agent
- install channels-setup and connect my agent to Slack
- set up a channel for my CopilotKit agent in Teams
- run the full channels-setup workflow for my project
How to install channels-setup
1Skills CLI (Vercel)
npx skills add CopilotKit/CopilotKit --skill channels-setup -a claude-code2Manually: put the files in place
~/.claude/skills/channels-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/channels-setup/
1Skills CLI (Vercel)
npx skills add CopilotKit/CopilotKit --skill channels-setup -a codex2Manually: put the files in place
.agents/skills/channels-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add CopilotKit/CopilotKit --skill channels-setup -a cursor2Manually: put the files in place
.cursor/skills/channels-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install CopilotKit/CopilotKit channels-setup2Manually: put the files in place
.github/skills/channels-setup/SKILL.md1Skills CLI (Vercel)
npx skills add CopilotKit/CopilotKit --skill channels-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/CopilotKit/CopilotKit --path skills/channels-setupManually: put the files in place
.devin/skills/channels-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add CopilotKit/CopilotKit --skill channels-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set6
The whole set →Similar
Questions about channels-setup
How do I install channels-setup in Claude Code?
Run npx skills add CopilotKit/CopilotKit --skill channels-setup -a claude-code. The skill will appear at ~/.claude/skills/channels-setup/SKILL.md.
What does channels-setup do?
It runs an interactive graph that guides you through building a CopilotKit agent in Slack or Teams: from checking your project to starting the host and proving your agent replies to a mention.
What should I do if the `npx --yes copilotkit@latest onboard start` command fails?
Stop and show the error. Don't try to recreate the workflow by hand — the graph updates, and it's better to run it again.
Source text
SKILL.md · MIT
--- name: channels-setup description: > Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams: "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding the project, building the AG-UI agent, creating and reconciling the managed Channel with the public CopilotKit CLI, running the long-running host, and proving a real provider mention gets a reply. The workflow is not in this file. Run `npx --yes copilotkit@latest onboard start` and follow the graph it prints. version: 1.0.0 --- # Set up a CopilotKit Channel The workflow is **not written down here**. Run this command: ```bash npx --yes copilotkit@latest onboard start ``` Then follow the graph it prints, start to finish. If the command asks for a CopilotKit CLI session check, you have permission to run it. Never reveal credentials. ## Do this 1. Run `npx --yes copilotkit@latest onboard start`. 2. Follow the graph it prints, start to finish. The graph asks for its own inputs. Do not pre-empt those questions. Do not substitute remembered channel-setup steps for what the graph says. Remembered steps are the reason this file is a pointer. ## If the command fails Stop. Tell the user the command failed. Show them the output. Ask them to retry. Do not improvise the workflow from memory. It spans the CopilotKit CLI, a managed Channel, provider setup the user does in Slack or Azure, and a long-running runtime host. A half-remembered version produces a project that installs cleanly and answers nothing. That is the most expensive failure available here. It looks finished.
© CopilotKit · MIT · CopilotKit/CopilotKit