channels-setup
Skill0 starsChanged 2 months agoMITView on GitHub
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 — it is fetched from https://copilotkit.ai/channels-guide.md at run time, so it cannot go stale against the CLI.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- CopilotKit/CopilotKitedited, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- CopilotKit/CopilotKit★ 39k58% same
Wrote their own version · 0
None found.
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 repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- angular-developerSkill
- copilotkit-channelsSkill
- copilotkit-cliSkill
- copilotkitSkill
- csharp-asyncSkill
- csharp-docsSkill
- csharp-xunitSkill
- ef-coreSkill
- github-actions-efficiencySkill
- github-actions-hardeningSkill
- github-actions-runtime-upgrade-conventionsSkill
- inspector-docsSkill
- inspector-workbenchSkill
- intelligence-docsSkill
- microsoft-agent-frameworkSkill
- microsoft-docsSkill
- ngrx-signal-storeSkill
- prdSkill
- setup-slack-channelSkill
- technical-writingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Verify you actually got the guide (below).
- Distinctive: line 27
Follow it exactly, start to finish.
- Distinctive: line 44
If any of those fail, you did not get the guide — treat it as unavailable no matter what the status code said.
- Distinctive: line 49
Stop. Tell the user you could not reach the guide, show them the URL, and ask them to paste its contents or retry.
- Distinctive: line 52
Do not improvise the workflow from memory.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up a CopilotKit Channel
The workflow is not written down here. It lives at one canonical URL so it is corrected in one place instead of on every surface that describes it:
https://copilotkit.ai/channels-guide.md
Do this
- Fetch
https://copilotkit.ai/channels-guide.md. - Verify you actually got the guide (below).
- Follow it exactly, start to finish.
The guide asks for its own inputs — the target project, the agent's real job, Slack or Microsoft Teams, and the agent framework and model. Do not pre-empt those questions, and do not substitute remembered channel-setup steps for what the guide says. Remembered steps are the reason this file is a pointer.
Verify you actually got the guide
A missing guide does not return 404. The site answers unknown paths with a "Page not found" HTML page under HTTP 200, so a successful status code proves nothing. Check the body instead:
- It is markdown, not HTML.
- It begins with
# Build and prove a CopilotKit Channels agent. - It contains five
## Phaseheadings.
If any of those fail, you did not get the guide — treat it as unavailable no matter what the status code said.
If you did not get the guide
Stop. Tell the user you could not reach the guide, show them the URL, and ask them to paste its contents or retry.
Do not improvise the workflow from memory. It spans the CopilotKit CLI, a managed Channel, provider setup performed by the user in Slack or Azure, and a long-running runtime host. A half-remembered version produces a project that installs cleanly and answers nothing, which is the most expensive failure available here — it looks finished.
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.

