Kuldeep Reddy avatar

Kuldeep Reddy

Community

@23wj1a0541

1Followers
|
27Public Repos
|
11Published Skills

Kuldeep Reddy maintains skills for building CopilotKit v2 in-app copilots, AG-UI protocol agent backends, and MCP servers with the mcp-use framework.

Skills Distribution
DomainDeveloper To...CopilotKit Applica.. (45%)AG-UI Protocol & A.. (25%)MCP Server Enginee.. (20%)Open-Source Contri.. (10%)

Agent Skills by Kuldeep Reddy

Showing 11 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Kuldeep Reddy

FAQPage Schema
What tasks can I accomplish with Kuldeep Reddy's CopilotKit skills?▼

You can set up new CopilotKit projects, add chat interfaces, register frontend actions, share application context with agents, handle interrupts, migrate v1 apps to v2, debug streaming and runtime connectivity failures, and wire external frameworks like LangGraph, CrewAI, or PydanticAI via AG-UI.

Who are these CopilotKit and MCP skills designed for?▼

Frontend and full-stack engineers building in-app copilots with CopilotKit v2, backend developers implementing custom agent backends over the AG-UI protocol, and contributors forking the CopilotKit monorepo or building MCP servers with the mcp-use framework.

How do I build an MCP server using these skills?▼

Consult the mcp-apps-builder skill first, as it is mandatory for all MCP server work. It covers mcp-use framework patterns for creating servers, defining server.tool(), server.resource(), and server.prompt() handlers, plus widgets, security patterns, and common pitfalls. Deprecated mcp-builder and chatgpt-app-builder skills redirect to mcp-app-builder.

How do I migrate a CopilotKit v1 application to v2?▼

Use the copilotkit-upgrade skill. It guides updating package imports, replacing deprecated hooks and components, switching from the GraphQL runtime to the AG-UI protocol runtime, and resolving breaking changes introduced in CopilotKit v2.

How do I diagnose CopilotKit runtime or streaming failures?▼

Use the copilotkit-debug skill. It covers runtime connectivity failures, agents not responding, streaming errors, action execution problems, transcription failures, version mismatches, and AG-UI event tracing to isolate where the frontend-to-agent communication breaks down.