// Use when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
Use when building custom agent backends, implementing the AG-UI protocol, debugging streaming issues, or understanding how agents communicate with frontends. Covers event types, SSE transport, AbstractAgent/HttpAgent patterns, state synchronization, tool calls, and human-in-the-loop flows.
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
Use when the user wants to update, refresh, or reinstall the CopilotKit agent SKILLS (the SKILL.md files that teach this agent about CopilotKit). NOT for updating the CopilotKit codebase or project — this is specifically about refreshing the skills/knowledge this agent has loaded. Triggers on "update copilotkit skills", "update skills", "refresh skills", "skills are stale", "skills are outdated", "get latest skills", "my copilotkit knowledge is wrong", "copilotkit APIs changed", "skills seem old", "wrong API names", "reinstall skills", "skills not working right", "update your copilotkit knowledge".
| name | copilotkit |
| description | Use when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task. |
| user_invocable | true |
| argument_hint | <task> |
Route to the appropriate sub-skill based on the user's task. If the task is ambiguous, ask one clarifying question before routing.
If the user wants to add CopilotKit to their project, or the request is general/unclear, route here:
copilotkit-setup — Install packages, configure the runtime, wire up the provider, get a working chat UI.
| Task | Sub-skill |
|---|---|
| Initial setup, installation, adding CopilotKit to a project | copilotkit-setup |
| Building features — frontend tools, shared state, generative UI, actions | copilotkit-develop |
| Connecting agent frameworks — LangGraph, CrewAI, Mastra, Pydantic AI, etc. | copilotkit-integrations |
| Debugging errors, fixing runtime issues, troubleshooting | copilotkit-debug |
| Upgrading versions, migrating between APIs | copilotkit-upgrade |
| AG-UI protocol — building custom backends, event streaming, debugging protocol issues | copilotkit-agui |
| Contributing to the CopilotKit repo | copilotkit-contribute |
| Update/refresh these skills, skills seem stale or wrong | copilotkit-self-update |
The copilotkit-docs MCP server at mcp.copilotkit.ai/mcp provides live documentation search. Use its tools for up-to-date reference material:
search-docs — search CopilotKit documentation by topicsearch-code — search CopilotKit source code and examplessearch-ag-ui-docs — search AG-UI protocol documentationsearch-ag-ui-code — search AG-UI TypeScript SDK sourcePrefer MCP lookups over hardcoded knowledge when answering specific API or configuration questions.