livekit/agent-skills

Agent Skills and a Claude Code plugin for building, testing, and shipping voice agents with LiveKit

7 skills listed · MIT · 74 stars · last pushed 27 Oct 2026

An official collection: published from the livekit organisation on GitHub.

livekit/agent-skills on GitHub

Across these 7 skills

Pattern check

Nothing flagged in 7

What it can touch

4 run shell commands

Checked at commit e1195b4 on 3 Nov 2026.

Install the collection

Claude Code plugin

Installs the latest version, not the one we checked. Installs everything in the plugin, including any hooks, MCP servers and scripts our check doesn't cover.

claude plugin marketplace add livekit/agent-skills --scope user &&claude plugin install livekit@livekit --scope user

Any agent

Installs the latest version, not the one we checked. The skills CLI reports installs to skills.sh unless you set DISABLE_TELEMETRY=1.

npx skills@1.7.4 add livekit/agent-skills

Skills

Skills in livekit/agent-skills
Skill	What it can touch	Pattern check	Licence	Updated
building-livekit-agentsBuilds voice and chat AI agents with LiveKit Agents and LiveKit Cloud. Use when the user asks to "build a voice agent", "create a LiveKit agent", "add voice AI to my app", "implement handoffs", "structure an agent workflow", "my agent is slow / too chatty", "it says it booked but nothing was saved", "make it confirm before committing", "it keeps re-asking things the caller already said", or is writing code against the LiveKit Agents SDK. Covers architecture: designing for latency, keeping context small, splitting a monolithic agent into handoffs and tasks, and designing for voice. Also covers keeping the model in charge of meaning while code owns state, approvals, and effects. For API specifics use reading-livekit-docs. To check behavior use debugging-livekit-agents and testing-livekit-agents. Instructions only Pattern check: Nothing flaggedMITUpdated 21 Oct 2026	Instructions only	Pattern check: Nothing flagged	MIT	21 Oct 2026
debugging-livekit-agentsDrives a live multi-turn conversation with a LiveKit agent running locally, using `lk agent debugger`. Use when the user says "test my agent", "try my agent", "does this work", or "why did it call that tool", after editing an agent to check how it behaves, or when an agent on a speech-to-speech model or one that mishears users needs checking. The default for a bare "test"; for regression tests use testing-livekit-agents, for graded runs running-livekit-simulations. Runs shell commands Pattern check: Nothing flaggedMITUpdated 9 Oct 2026	Runs shell commands	Pattern check: Nothing flagged	MIT	9 Oct 2026
operating-livekit-agentsDeploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside worker processes, provider timeouts and degradation, graceful shutdown, SDK upgrades, and observability. Use when the user says "deploy my agent", "roll back the deployment", "tail the agent logs", "the first call after a restart is slow", "attached to a different loop / event loop is closed", "prewarm the VAD", "shut down without dropping calls", "upgrade livekit-agents safely", "correlate logs by session", or is changing an agent codebase that is already live. Not for designing the agent (building-livekit-agents) or reproducing one bad conversation locally (debugging-livekit-agents). Instructions only Pattern check: Nothing flaggedMITUpdated 24 Sept 2026	Instructions only	Pattern check: Nothing flagged	MIT	24 Sept 2026
reading-livekit-docsLooks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory. Use whenever a question touches LiveKit specifics: "does LiveKit support X", "what changed in agents 1.8", "what are the arguments to Y", "how much does LiveKit cost", "find an example of Z in the LiveKit repos", or before writing any LiveKit code. Other LiveKit skills load this one first. Covers the LiveKit Docs MCP server and the `lk docs` CLI. Runs shell commands Pattern check: Nothing flaggedMITUpdated 24 Sept 2026	Runs shell commands	Pattern check: Nothing flagged	MIT	24 Sept 2026
running-livekit-simulationsRuns LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and interruptions", or wants to check whole-conversation behavior before shipping. Covers text and audio mode and what each catches, running against a local or deployed agent, degraded-audio flags, automating a pre-release run, and triaging failures with list, view and export. For writing the scenarios use writing-livekit-scenarios. Not the default for a bare "test my agent", which goes to debugging-livekit-agents. Use this skill when the user names simulations, scenarios, a run, CI, or shipping. Runs shell commands Pattern check: Nothing flaggedMITUpdated 24 Sept 2026	Runs shell commands	Pattern check: Nothing flagged	MIT	24 Sept 2026
testing-livekit-agentsWrites turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js). Use when the user asks to "write tests for my agent", "add a test for this tool", "test the handoff", "pin this bug", "why does my agent test fail", or after building or changing agent behavior that needs regression coverage. Covers the SDK's test session harness, assertions on messages, tool calls and handoffs, LLM judging of a reply against an intent, mocking tools, multi-turn tests, and judging whole conversations with the built-in judges. For interactive poking use debugging-livekit-agents. For grading whole conversations at scale use running-livekit-simulations. Instructions only Pattern check: Nothing flaggedMITUpdated 24 Sept 2026	Instructions only	Pattern check: Nothing flagged	MIT	24 Sept 2026
writing-livekit-scenariosCreates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my real database", "seed state per scenario", "it passed but booked the wrong thing", "grade the final state", or wants to stress-test a flow before shipping. Covers generating a baseline with the LiveKit scenario generator and refining it, writing the cases generation misses, phrasing simulated-user instructions so they steer reliably, splitting scenarios into sets across files, and the agent-side code that seeds deterministic state from a scenario and fails a run on its final state. To run them use running-livekit-simulations. Runs shell commands Pattern check: Nothing flaggedMITUpdated 24 Sept 2026	Runs shell commands	Pattern check: Nothing flagged	MIT	24 Sept 2026