Keeps CopilotKit documentation aligned with released Inspector panels, the views shown in its local web overlay. It updates reader guidance and panel mappings when panels change, and checks quickstart instructions against supported platforms.
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.
Review the instructions the agent will receive before you install.
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.
references/pane-map.md before proceeding.no page yet in the map. Do not invent a page.references/pane-map.md in the same change.references/pane-map.md before proceeding.The default web quickstart includes a numbered step after the first chat:
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 |
no page yet in the map. Do not create a new docs section unless the user asked for one.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up an agent that replies in Slack or Microsoft Teams using CopilotKit's guided CLI workflow. It covers project preparation, agent creation, channel configuration, a persistent host process, and verification with a real message.
Guides development of ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK, covering server tools, React interfaces, and shared state. This skill is deprecated and directs users to mcp-app-builder.
Helps integrate CopilotKit into an app by consulting current documentation and source code. Covers chat interfaces, agent connections, shared state, and troubleshooting, with guidance on checking configuration and avoiding incompatible API versions.
Implement and customize managed CopilotKit Channels so agents can reply in Slack or Microsoft Teams. It covers channel handlers, persistent runtime connections, Teams setup, and checks for silent failures such as missing permissions or incompatible package versions.
Use the CopilotKit CLI to check app connections, credentials, and agent responses before investigating code. It also guides project creation, integration into existing apps, hosted project selection, typed agent identifier generation, and thread history imports.
Develop and debug CopilotKit Inspector interfaces in a dedicated local workbench. It guides baseline screenshots, visual checks after each change, and additional narrow-screen or theme checks when layout or contrast is involved.