Restructure a slow voice agent
Ask your coding agent to review an agent with long prompts, too many tools or awkward handoffs. The building skill guides decisions about context size, latency and dividing a conversation into focused agents and tasks.
Guide your coding agent through building, debugging, testing and deploying LiveKit voice agents.
LiveKit Agent Skills gives AI coding agents guidance for developing voice agents with the LiveKit Agents SDK for Python and Node.js. It covers architecture, live debugging, regression tests, simulations and production operations, with documentation lookups for current APIs.
Describe the work you want done and the coding agent selects relevant skills. In Claude Code, you can also select a skill manually from the slash menu. The full plugin bundles the LiveKit Docs MCP server; the Skills CLI installs the skills separately.
Ask your coding agent to review an agent with long prompts, too many tools or awkward handoffs. The building skill guides decisions about context size, latency and dividing a conversation into focused agents and tasks.
Reproduce a conversation locally and inspect the tool calls, arguments and replies behind it. The debugging skill guides this loop through the LiveKit CLI, with text mode for conversation logic and audio mode for speech-related problems.
Turn a failed greeting, tool call or handoff into a regression test in your existing pytest or Vitest suite. The testing skill covers event assertions, tool mocks and judging replies against the intended outcome.
Create scenarios for callers who backtrack, change details or interrupt, then run them against a local or deployed agent. The scenario and simulation skills guide expectations, test state and failure analysis.
Simulations require a LiveKit Cloud project with the CLI authenticated to it. Generating scenarios from source uploads the code to LiveKit Cloud and asks for confirmation first. Audio runs exercise the speech pipeline and are metered at a higher rate than text runs.
Use the operating skill when deploying a version to LiveKit Cloud, planning a rollback or investigating slow startup and provider timeouts. Deployment requires an authenticated LiveKit Cloud project; the guidance also covers prewarming, graceful shutdown and SDK upgrades.
The skills cover different development tasks and refer the coding agent to one another when needed. For CLI-driven tasks, install or update the LiveKit CLI.
Showing all 7
Design voice agent workflows for low latency, focused handoffs and reliable state changes.
Debug local conversations by inspecting replies, tool calls and handoffs.
Deploy to LiveKit Cloud and troubleshoot performance, shutdown and provider failures.
Look up current LiveKit APIs, CLI options, changelogs and pricing.
Run text or audio simulations and investigate failed conversation outcomes.
Write regression tests for replies, tool calls and handoffs in pytest or Vitest.
Create simulation scenarios with clear expectations, seeded state and final-state checks.
No matching results.
Search LiveKit documentation, SDK source, changelogs and Cloud pricing.
Choose the Claude Code marketplace route for the full plugin. LiveKit CLI routes install the skills and add the Docs MCP server; Skills CLI routes install the skills alone. Use one installation method per coding agent to avoid duplicate skills.
This installs the LiveKit skills and Docs MCP server together in Claude Code.
Choose this instead of installing the same skills with the LiveKit CLI or Skills CLI. Duplicate copies load competing skill descriptions.
In a local Claude Code terminal session, add the LiveKit marketplace.
/plugin marketplace add livekit/agent-skillsOpen the LiveKit plugin’s installation panel, review its details, choose an installation scope and install it.
/plugin install livekit@livekitRead the installation result. If the plugin is active now, continue. If a reload is needed, close the panel to let Claude Code apply it; follow the panel’s instructions if activation remains pending.
Open the plugin manager and check that LiveKit is installed and enabled. Type a slash in chat and look for skills under the livekit namespace. Check that livekit-docs appears as connected among Claude Code’s MCP servers.
/pluginFor automatic updates, enable auto-update for the livekit marketplace under Marketplaces in the plugin manager.
This installs the LiveKit skills and adds the Docs MCP server to Claude Code. Choose this instead of the plugin or Skills CLI method for the same coding agent.
Install or update the LiveKit CLI to v2.19.0 or later. The commands below use the current project by default; for all projects, add --global to both commands.
Run this in a terminal from your project directory. In the coding-agent selection, keep Claude Code selected and clear any other agents you do not want to configure, then confirm the installation.
lk skills installIn the same terminal, list the installation. Check that the LiveKit skills are installed for Claude Code and that its Docs MCP server setup is listed.
lk skills listStart a new Claude Code session in the project and check its available skills for building-livekit-agents. Check that livekit-docs appears as connected among Claude Code’s MCP servers.
This installs the LiveKit skills for Claude Code without the plugin’s bundled Docs MCP server. Choose this instead of the plugin or LiveKit CLI method for the same coding agent.
Run this in a terminal from your project directory. Select Claude Code as the target coding agent and install the LiveKit skills. Skills CLI installs to the current project by default.
npx skills add livekit/agent-skillsStart a new Claude Code session in the project and check its available skills for building-livekit-agents and the other LiveKit skills.
For documentation lookups, the skills can use the LiveKit CLI or a separately connected LiveKit Docs MCP server.
This installs the LiveKit skills and adds the Docs MCP server to Cursor. Choose this instead of the Skills CLI method for the same coding agent.
Install or update the LiveKit CLI to v2.19.0 or later. The commands below use the current project by default; for all projects, add --global to both commands.
Run this in a terminal from your project directory. In the coding-agent selection, keep Cursor selected and clear any other agents you do not want to configure, then confirm the installation.
lk skills installIn the same terminal, list the installation. Check that the LiveKit skills are installed for Cursor and that its Docs MCP server setup is listed.
lk skills listRestart Cursor so it discovers the installed skills. In Agent chat, type a slash and search for building-livekit-agents to check that it is available.
This installs the LiveKit skills for Cursor without the Claude Code plugin’s bundled Docs MCP server. Use one installation method for these skills in Cursor.
Run this in a terminal from your project directory. Select Cursor as the target coding agent and install the LiveKit skills. Skills CLI installs to the current project by default.
npx skills add livekit/agent-skillsRestart Cursor so it discovers the installed skills. In Agent chat, type a slash and search for building-livekit-agents to check that it is available.
For documentation lookups, the skills can use the LiveKit CLI or a separately connected LiveKit Docs MCP server.
This installs the LiveKit skills and adds the Docs MCP server to Codex. Choose this instead of the Skills CLI method for the same coding agent.
Install or update the LiveKit CLI to v2.19.0 or later. The commands below use the current project by default; for all projects, add --global to both commands.
Run this in a terminal from your project directory. In the coding-agent selection, keep Codex selected and clear any other agents you do not want to configure, then confirm the installation.
lk skills installIn the same terminal, list the installation. Check that the LiveKit skills are installed for Codex and that its Docs MCP server setup is listed.
lk skills listOpen the project in Codex and check its available skills for building-livekit-agents. In the desktop app, use Skills in the sidebar. Codex detects skill changes automatically; restart it if the new skills do not appear. Check Codex’s active MCP servers for livekit-docs.
This installs the LiveKit skills for Codex without the Claude Code plugin’s bundled Docs MCP server. Use one installation method for these skills in Codex.
Run this in a terminal from your project directory. Select Codex as the target coding agent and install the LiveKit skills. Skills CLI installs to the current project by default.
npx skills add livekit/agent-skillsOpen the project in Codex and check its available skills for building-livekit-agents. In the desktop app, use Skills in the sidebar. Codex detects skill changes automatically; restart it if the new skills do not appear.
To let Codex look up LiveKit documentation through MCP, run this in a terminal.
codex mcp add --url https://docs.livekit.io/mcp livekit-docsCheck Codex’s active MCP servers for livekit-docs. The skills can also use the LiveKit CLI for documentation lookups.