How do I install the Copilotkit skill?

Run npx skillmds add majiayu000/copilotkit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Copilotkit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Copilotkit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Copilotkit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Copilotkit?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Copilotkit by majiayu000 — Agent Skill

Name: Copilotkit
Rating: 4.2 (5 reviews)
Author: majiayu000

Copilotkit

CopilotKit integration patterns for providers, runtime wiring, `useCoAgent`, `useCopilotAction`, `useLangGraphInterrupt`, shared state, and HITL with LangGraph. Use when building agent-native product UX.

majiayu000 a85bfe3 2 files · 3.1 KB Updated Sep 9, 2026 567 repo stars

File contents

CopilotKit

Use this skill to implement CopilotKit-based agent UX with correct provider wiring, runtime selection, shared state, frontend actions, and interrupt handling.

Quick Triage

Use this skill for CopilotKit provider setup, runtime endpoints, hooks, shared-state rendering, and human-in-the-loop UX.
Switch to $langgraph when backend graph behavior is the main issue.
Switch to $ag-ui when protocol event compliance is the main issue.
Switch to $langchain when core model/tool orchestration logic is the main issue.

Workflow

Choose runtime topology. Decide LangGraph platform endpoint vs remote backend runtime before UI edits.
Configure provider boundary. Set <CopilotKit> provider and runtime endpoint settings first.
Select hooks by responsibility. Use useCoAgent for state coupling, useCopilotAction for frontend actions, and interrupt hooks for HITL flow.
Define shared state contract. Separate input/output/internal state and keep serialization stable.
Implement HITL path. Map interrupt payloads to explicit frontend action handlers.
Implement persistence behavior. Choose thread/message persistence strategy and ensure resume consistency.
Validate end-to-end UX. Test streaming, tool visibility, shared-state render, and resume flow.

Default Patterns

Keep runtime and UI concerns separated.
Keep shared-state schema explicit and minimal.
Keep action handlers idempotent.
Treat interrupts as typed control flow, not free-form messages.

Failure Modes

Endpoint mismatch (wrong runtime URL/type).
Hooks bound to wrong agent name or provider scope.
Shared-state updates not reflected due schema mismatch.
Interrupt action handlers not wired to expected payload type.

Reference Map

Load only what is needed for the current subtask.

Runtime and provider setup: references/runtime-and-provider.md
Hooks and actions: references/hooks-and-actions.md
CoAgents and shared state: references/coagents-shared-state.md
HITL and troubleshooting: references/hitl-and-troubleshooting.md

---name: copilotkitdescription: CopilotKit integration patterns for providers, runtime wiring, `useCoAgent`, `useCopilotAction`, `useLangGraphInterrupt`, shared state, and HITL with LangGraph. Use when building agent-native product UX.--- # CopilotKit Use this skill to implement CopilotKit-based agent UX with correct provider wiring, runtime selection, shared state, frontend actions, and interrupt handling. ## Quick Triage - Use this skill for CopilotKit provider setup, runtime endpoints, hooks, shared-state rendering, and human-in-the-loop UX. - Switch to `$langgraph` when backend graph behavior is the main issue. - Switch to `$ag-ui` when protocol event compliance is the main issue. - Switch to `$langchain` when core model/tool orchestration logic is the main issue. ## Workflow 1. Choose runtime topology. Decide LangGraph platform endpoint vs remote backend runtime before UI edits. 2. Configure provider boundary. Set `<CopilotKit>` provider and runtime endpoint settings first. 3. Select hooks by responsibility. Use `useCoAgent` for state coupling, `useCopilotAction` for frontend actions, and interrupt hooks for HITL flow. 4. Define shared state contract. Separate input/output/internal state and keep serialization stable. 5. Implement HITL path. Map interrupt payloads to explicit frontend action handlers. 6. Implement persistence behavior. Choose thread/message persistence strategy and ensure resume consistency. 7. Validate end-to-end UX. Test streaming, tool visibility, shared-state render, and resume flow. ## Default Patterns - Keep runtime and UI concerns separated. - Keep shared-state schema explicit and minimal. - Keep action handlers idempotent. - Treat interrupts as typed control flow, not free-form messages. ## Failure Modes - Endpoint mismatch (wrong runtime URL/type). - Hooks bound to wrong agent name or provider scope. - Shared-state updates not reflected due schema mismatch. - Interrupt action handlers not wired to expected payload type. ## Reference Map Load only what is needed for the current subtask. - Runtime and provider setup: `references/runtime-and-provider.md` - Hooks and actions: `references/hooks-and-actions.md` - CoAgents and shared state: `references/coagents-shared-state.md` - HITL and troubleshooting: `references/hitl-and-troubleshooting.md`

Frequently asked questions