Overview
LiveKit publishes Agent Skills that teach coding agents like Claude Code, Cursor, and Codex how to build, test, and ship voice agents with the LiveKit Agents SDK for Python and Node.js. The skills are open source and live in the livekit/agent-skills repository.
For a broader guide on setting up coding agents with LiveKit expertise, including docs search and the agent debugger, see Coding agent support.
Skills
Each skill covers one job in the development loop and hands off to the others by name, so a task loads only the skills it needs. Coding agents pick them up from what you ask for, so you don't need to invoke them by name.
| Skill | What it does |
|---|---|
reading-livekit-docs | Looks up current LiveKit facts through the Docs MCP server or lk docs instead of answering from memory. The other skills load it first. |
building-livekit-agents | Guides agent architecture: latency, small context, handoffs and tasks, and designing for voice. |
debugging-livekit-agents | Drives a multi-turn text conversation with the agent running locally, using lk agent debugger. The default way to check a change. |
testing-livekit-agents | Writes turn-level tests in the project's pytest or Vitest suite. |
writing-livekit-scenarios | Creates the scenarios a simulation runs, and wires the agent to seed and grade state from them. |
running-livekit-simulations | Runs simulations locally or in CI, and triages the failures. |
operating-livekit-agents | Deploys an agent to LiveKit Cloud, rolls back, and keeps a live agent healthy: prewarming, timeouts, graceful shutdown, and SDK upgrades. |
The skills send the agent to the docs for API details rather than restating them, so they work best alongside the Docs MCP server or lk docs. The Claude Code plugin sets up the Docs MCP server for you.
Installation
Choose one install method per coding agent. Installing the same skills twice, for example as a Claude Code plugin and with npx skills, loads both copies, so every skill competes with itself.
Install the LiveKit plugin. It includes the skills and the Docs MCP server.
/plugin marketplace add livekit/agent-skills/plugin install livekit@livekit
Plugin skills are namespaced. To invoke one manually, use /livekit:building-livekit-agents rather than /building-livekit-agents.
To receive skill updates automatically, turn on auto-update for the livekit marketplace in /plugin, under Marketplaces. Otherwise, run /plugin marketplace update livekit to update.
Install the skills with the skills CLI , which supports most coding agents:
npx skills add livekit/agent-skills
You can also install from the discovery index with npx skills add https://livekit.com. To update, run npx skills update.
To install by hand, copy the skill directories you want from skills/ into your coding agent's skills directory. For example, .claude/skills/ in a project for Claude Code, or .agents/skills/ for agents that read the shared directory.
Updates
The published skills always track the main branch of livekit/agent-skills, and every merged change is a release. Skills don't have version numbers. Each install method identifies a skill by its content instead:
npx skillsrecords a hash of each installed skill in a lock file,skills-lock.jsonin a project, and compares it to the published skill when you update.- The Claude Code plugin picks up new commits to livekit/agent-skills whenever its marketplace updates.
- The discovery index publishes a SHA-256 digest of each skill.
When a skill is renamed or removed, the discovery index and the Claude Code plugin drop it with their next update.
If you installed the earlier livekit-agents or livekit-simulations skills, delete them and install the current skills. They were replaced by the skills listed above.
Discovery index
LiveKit also publishes the skills at https://livekit.com in the Agent Skills discovery format, so any tool that supports the standard can list and install them from there. The index includes a SHA-256 digest of each skill and updates whenever the skills change.