channels-setup

backendcopilotkit

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 g

Install

npx skills add https://github.com/copilotkit/copilotkit --skill channels-setup

SKILL.md

---name: channels-setupdescription: >get it answering in Slack or Microsoft Teams: set up a channel", "connect mywanting a working channel end to end. Covers the whole path: inspecting orversion: 1.0.0---

Set up a CopilotKit Channel

The workflow is not written down here. Run this command:

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

Run npx --yes copilotkit@latest onboard start.
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.

Related skills

entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servic entra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app regist supabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb