
Livekit Agents
Scaffold voice AI agents on LiveKit Cloud with the Agents SDK, opinionated Cloud + Inference guidance, handoffs, and mandatory tests before you ship realtime voice.
Overview
livekit-agents is an agent skill for the Build phase that guides voice AI agents on LiveKit Cloud with mandatory tests and live-doc-sourced API details.
Install
npx skills add https://github.com/livekit/agent-skills --skill livekit-agentsWhat is this skill?
- Mandatory pre-code checklist: read full skill, connect LiveKit Cloud (`LIVEKIT_URL`, API key/secret), plan docs lookup,
- Opinionated path: LiveKit Cloud + LiveKit Inference (not self-hosted defaults)
- Covers voice agents, handoffs, and structured agent workflows per user intent
- Every implementation must include tests—non-optional requirement in skill description
- API facts must come from live docs (MCP or web search), not stale assumptions in the skill text
- Mandatory 4-item pre-code checklist before any implementation
- Tests required for every agent implementation (explicit in skill description)
- Skill metadata version 0.3.1
Adoption & trust: 2.4k installs on skills.sh; 55 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want a realtime voice agent on LiveKit but lack a consistent Cloud-first path, handoff patterns, and a testing discipline agents often skip.
Who is it for?
Solo builders shipping voice features on LiveKit Cloud who will write tests and keep docs lookup in the loop.
Skip if: Quick prototypes that skip tests, or self-hosted-only stacks expecting LiveKit Inference guidance to apply unchanged.
When should I use this skill?
User asks to build a voice agent, create a LiveKit agent, add voice AI, implement handoffs, or structure agent workflows with LiveKit Agents SDK.
What do I get? / Deliverables
You start from a completed Cloud checklist and opinionated Agents SDK structure, implement handoffs/workflows with tests, and verify APIs against current LiveKit documentation.
- Voice agent implementation with structured workflows/handoffs
- Automated tests covering the agent implementation
Recommended Skills
Journey fit
Voice agent implementation is core Build agent-tooling for solo builders adding realtime speech to products. Agent-tooling is where LiveKit session design, SDK structure, and Cloud credentials land in code.
How it compares
Opinionated LiveKit Cloud voice workflow with required tests—not a generic LLM chat wrapper skill.
Common Questions / FAQ
Who is livekit-agents for?
Indie developers and small teams building voice AI with LiveKit Agents SDK on LiveKit Cloud who need handoffs, workflows, and enforced test coverage.
When should I use livekit-agents?
In Build agent-tooling when users ask to build a voice agent, add voice AI, create a LiveKit agent, or structure handoffs—after Cloud credentials are available.
Is livekit-agents safe to install?
It expects Cloud API secrets and network access to LiveKit; review the Security Audits panel on this page and never commit keys to the repo.
SKILL.md
READMESKILL.md - Livekit Agents
# LiveKit Agents Development for LiveKit Cloud This skill provides opinionated guidance for building voice AI agents with LiveKit Cloud. It assumes you are using LiveKit Cloud (the recommended path) and encodes *how to approach* agent development, not API specifics. All factual information about APIs, methods, and configurations must come from live documentation. **This skill is for LiveKit Cloud developers.** If you're self-hosting LiveKit, some recommendations (particularly around LiveKit Inference) won't apply directly. ## MANDATORY: Read This Checklist Before Starting Before writing ANY code, complete this checklist: 1. **Read this entire skill document** - Do not skip sections even if MCP is available 2. **Ensure LiveKit Cloud project is connected** - You need `LIVEKIT_URL`, `LIVEKIT_API_KEY`, and `LIVEKIT_API_SECRET` from your Cloud project 3. **Set up documentation access** - Use MCP if available, otherwise use web search 4. **Plan to write tests** - Every agent implementation MUST include tests (see testing section below) 5. **Verify all APIs against live docs** - Never rely on model memory for LiveKit APIs This checklist applies regardless of whether MCP is available. MCP provides documentation access but does NOT replace the guidance in this skill. ## LiveKit Cloud Setup LiveKit Cloud is the fastest way to get a voice agent running. It provides: - Managed infrastructure (no servers to deploy) - **LiveKit Inference** for AI models (no separate API keys needed) - Built-in noise cancellation, turn detection, and other voice features - Simple credential management ### Connect to Your Cloud Project 1. Sign up at [cloud.livekit.io](https://cloud.livekit.io) if you haven't already 2. Create a project (or use an existing one) 3. Get your credentials from the project settings: - `LIVEKIT_URL` - Your project's WebSocket URL (e.g., `wss://your-project.livekit.cloud`) - `LIVEKIT_API_KEY` - API key for authentication - `LIVEKIT_API_SECRET` - API secret for authentication 4. Set these as environment variables (typically in `.env.local`): ```bash LIVEKIT_URL=wss://your-project.livekit.cloud LIVEKIT_API_KEY=your-api-key LIVEKIT_API_SECRET=your-api-secret ``` The LiveKit CLI can automate credential setup. Consult the CLI documentation for current commands. ### Use LiveKit Inference for AI Models **LiveKit Inference is the recommended way to use AI models with LiveKit Cloud.** It provides access to leading AI model providers—all through your LiveKit credentials with no separate API keys needed. Benefits of LiveKit Inference: - No separate API keys to manage for each AI provider - Billing consolidated through your LiveKit Cloud account - Optimized for voice AI workloads Consult the documentation for available models, supported providers, and current usage patterns. The documentation always has the most up-to-date information. ## Critical Rule: Never Trust Model Memory for LiveKit APIs LiveKit Agents is a fast-evolving SDK. Model training data is outdated the moment it's created. When working with LiveKit: - **Never assume** API signatures, method names, or configuration options from memory - **Never guess** SDK behavior or default values - **Always verify** against live documentation before writing code - **Always cite** the documentation source when implementing features This rule applies even when confident about an API. Verify anyway. ## REQUIRED: Use LiveKit MCP Server for Documentation Before writing any LiveKit code, ensur