agentleFS
RorroRojas3RorroRojas3/maf-agents/.claude/skills/channels-setup/SKILL.md

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

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
  1. Distinctive:

    Verify you actually got the guide (below).

    line 26
  2. Distinctive:

    Follow it exactly, start to finish.

    line 27
  3. Distinctive:

    If any of those fail, you did not get the guide — treat it as unavailable no matter what the status code said.

    line 44
  4. Distinctive:

    Stop. Tell the user you could not reach the guide, show them the URL, and ask them to paste its contents or retry.

    line 49
  5. Distinctive:

    Do not improvise the workflow from memory.

    line 52

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Fetch https://copilotkit.ai/channels-guide.md.
  2. Verify you actually got the guide (below).
  3. 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 ## Phase headings.

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.