Slack and Teams Channels
Customizes a CopilotKit Intelligence Channel for Slack or Microsoft Teams.
Install
npx skills add CopilotKit/CopilotKit --skill copilotkit-channels -g -a claude-code -y- Repository
- CopilotKit/CopilotKit38.5k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or, for a project the CLI did not generate, writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope, because the CLI or dashboard wizard performs it. Creating a Slack app for the first time is not: if no Slack app exists yet, use setup-slack-channel for the provider half and return here for the code.
CopilotKit Channels
Managed Channels let an agent answer in Slack or Microsoft Teams. Intelligence owns the provider edge, signed ingress, egress, credential storage, and delivers turns to your runtime over its realtime transport.
Scope
This skill covers managed Intelligence Channels: CopilotIntelligenceRuntime, app-api Channel resources, and the realtime gateway.
It does not cover the self-hosted @copilotkit/channels provider adapters (@copilotkit/channels-slack, -teams, -discord, -whatsapp). Those hold provider credentials in your process and talk to the provider directly. Both products use the words "channels" and "Slack", so confirm which one the user means before wiring anything. If they want to hold their own Slack tokens and run their own ingress, they want the adapter packages, not this skill.
Decide which path you are on first
Everything below depends on this, and getting it wrong produces a project with two Channel declarations that fight over one Channel.
Look for channel-host.mts at the project root.
