Individual skill
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setup_required, sits at "Waiting for runtime", the Channel is Online but a Slack mention gets no reply, or a Slack app was built with Socket Mode instead of an Intelligence Request URL. Scoped to an OpenTag checkout, or the OpenTag example inside a channels-sdk clone — the phases assume those conventions (app/channel.tsx, app/env.ts, INTELLIGENCE_CHANNEL_NAME, a local agent on port 8123) and do not describe a project scaffolded by copilotkit init, which already ships its own channel host. If the Slack app and Channel already exist and the question is about declaring or customising the Channel in code, use the copilotkit-channels skill instead.
skills/setup-slack-channel/SKILL.md
Source commit d168487e7a753a1527256c7e4c79344377f3d092
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 38,551
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- llm Repository topic
- nextjs Repository topic
- open-source Repository topic
- react Repository topic
- reactjs Repository topic
- ts Repository topic
- typescript Repository topic
- agent Repository topic
- agents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 26,033 bytesSKILL.mdcore · 26,033 bytesSKILL.mdcore · 26,033 bytesSKILL.mdcore · 26,033 bytesSKILL.mdcore · 26,033 bytesSKILL.mdcore · 26,033 bytesassets/slack-app-manifest.yamlasset · 4,748 bytesreferences/intelligence-channel.mddoc · 8,636 bytesreferences/local-runtime.mddoc · 7,937 bytesreferences/optional-e2e.mddoc · 4,785 bytesreferences/secrets-and-credentials.mddoc · 6,820 bytesreferences/slack-workspace-and-app.mddoc · 8,283 bytesreferences/troubleshooting.mddoc · 18,636 bytes
Read excerpt
# Set up a Slack Channel for a local Channels agent
Take a developer from a code checkout to a working local Slack agent. **Five
separate systems** have to line up, and they are owned by four different parties:
| System | Who owns it | Where you work on it |
| ----------------------------------------------------- | ----------------------------- | ---------------------------------------- |
| Slack workspace | Workspace owner / app manager | Slack, in a browser |
| Slack app + its tokens | The developer | api.slack.com, in a browser |
| Intelligence project, API key, Channel, Slack adapter | The developer | The Intelligence dashboard, in a browser |
| Local Channels runtime | The developer | This repo, in the shell |
| AG-UI agent backend | The developer | This repo, in the shell |
## How delivery actually works — two legs, two mechanisms