What problem does it solve? Debugging CopilotKit integrations is hard because failures can originate in the runtime, the agent, the SSE event stream, frontend tool registration, CORS, or version mismatches between packages. This Skill provides a structured diagnostic workflow that maps symptoms to root causes using error code catalogs and AG-UI event tracing. ## Core Features & Use Cases - Structured Diagnostic Workflow: A five-step process covering information gathering, error code lookup, AG-UI event tracing, root cause identification, and fix verification. - Error Code Catalog: Complete reference for v1 CopilotKitErrorCode, v2 CopilotKitCoreErrorCode, and TranscriptionErrorCode with causes and resolutions. - AG-UI Event Tracing: Documents expected event sequences (RunStarted, TextMessage, ToolCall, StateSnapshot, RunFinished) and known failure patterns like reasoning event stalls. - Use Case: Your CopilotKit chat connects but the agent never responds. The Skill walks you through checking the /info endpoint, inspecting the SSE stream in the Network tab, verifying the agent registration, and matching the error to known GitHub issues. ## Quick Start Use the copilotkit-debug skill to diagnose why my CopilotKit agent is not responding to chat messages.