channels-setup
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…
Keeps CopilotKit docs pointing at shipped Inspector panes so readers open the overlay. Use when adding, changing, renaming, or removing an Inspector pane, tab, or overlay action in @copilotkit/web-inspector, or when editing docs that mention Inspector. Don't use for Inspector UI
$ npx -y skills add CopilotKit/CopilotKit --skill inspector-docs --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/inspector-docsContext preview
The summary Claude sees to decide when to auto-load this skill.
Keeps CopilotKit docs pointing at shipped Inspector panes so readers open the overlay. Use when adding, changing, renaming, or removing an Inspector pane, tab, or overlay action in @copilotkit/web-inspector, or when editing docs that mention Inspector. Don't use for Inspector UI
name: inspector-docs description: > Keeps CopilotKit docs pointing at shipped Inspector panes so readers open the overlay. Use when adding, changing, renaming, or removing an Inspector pane, tab, or overlay action in @copilotkit/web-inspector, or when editing docs that mention Inspector. Don't use for Inspector UI polish that does not add a pane, for CLI or agent-prompt copy, or for unshipped Inspector ideas. version: 1.0.1
Inspector is the localhost overlay that shows Threads, Agents, and Learning. Every shipped pane that a reader can use must have a docs pointer. The pointer tells the reader to open Inspector and look at that pane.
Load this skill when:
Do not load it for icon, ping, layout, or copy-only Inspector changes that do not add a pane. Those UI changes use `inspector-workbench`.
If the same change also edits Inspector UI, load `inspector-workbench` as well and start the standalone lab.
1. Name the shipped pane using the label the reader sees in Inspector. 2. If mapping a pane, read `references/pane-map.md` before proceeding. 3. If the pane is not shipped, stop. Do not add a Callout. 4. If the map already has a page, open that page and confirm the Callout names this pane and what success looks like. 5. If the map has no page, add a Callout on the matching shared root docs page, or write `no page yet` in the map. Do not invent a page. 6. Update `references/pane-map.md` in the same change.
1. If removing a pane, read `references/pane-map.md` before proceeding. 2. Remove the Callout from the mapped page. 3. Delete the map row.
The default web quickstart includes a numbered step after the first chat:
1. **Agents** then **Agent**: the agent is listed. 2. Send a chat message. **Agents** then **AG-UI Events**: events are moving. 3. **Threads**: unlocked, or locked with Enable Intelligence.
Angular uses the shared step snippet, like every other web frontend: `@copilotkit/angular` auto-mounts a pinned `@copilotkit/web-inspector`, so there is no install step to link (OSS-948). React Native and Channels do not get this step at all.
| Signal | What it means | Do instead | | ---------------------------------------------------------------------- | ---------------------------------------------------- | ----------------------------------------------------------------- | | Callout names Playground, Fork, emit events, or another unshipped idea | Docs would advertise work that is not in the overlay | Stop. Record the idea under Unshipped in `references/pane-map.md` | | "Click the Inspector button" on React Native or Channels | Those surfaces have no web overlay | Skip the Open Inspector step | | Callout names a pane the overlay does not show | The pointer is a lie | Rewrite the Callout to a shipped pane, or remove it |
Docs · Examples · CopilotKit Intelligence · Build agent-native applications — on any framework, on any surface. Generative UI, shared state, and human-in-the-loop workflows for React, Angular, Vue, React Native — and in Slack and Microsoft Teams.
Repo: CopilotKit/CopilotKit
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…
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…
Use for the CopilotKit CLI — `npx copilotkit@latest`. Covers proving a project's wiring with `verify` before debugging anything by hand, scaffolding with…
Use for any CopilotKit question — adding it to an app, chat UI, frontend or server tools, generative UI, shared state, human-in-the-loop, agent frameworks…
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add,…
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when…