Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does.
Install Debugging Livekit Agents
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agents --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .claude/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .claude/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agents --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .agents/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .agents/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agents --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .cursor/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .cursor/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/livekit-examples/agent-starter-python.git --path .agents/skills/debugging-livekit-agents--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agents --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .gemini/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .gemini/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .github/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .github/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install livekit-examples/agent-starter-python debugging-livekit-agents --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/livekit-examples/agent-starter-python.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debugging-livekit-agents .opencode/skills/debugging-livekit-agents && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-livekit-agents" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/debugging-livekit-agents into .opencode/skills/debugging-livekit-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-livekit-agents", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-livekit-agents- GitHub stars
- 264
- Used in
- 1 other repo
- Token cost
- ~1.2k tokens
- SKILL.md length
- 585 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does.
- The user says test my agent
- SKILL.md covers The loop, Debugging with it, When to use something else and Related skills
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Why did it call that tool
What it does
Debugging Livekit Agents is an agent skill from livekit-examples/agent-starter-python. Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it behaves. Wraps lk agent debugger: start the agent in text mode, send turns, read the tool calls, handoffs, errors and logs behind each reply, and restart after an edit. It runs without audio or a…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging and Unit testing. The repository describes itself as: A complete voice AI starter for LiveKit Agents with Python. The licence is MIT.
When your agent uses it
- The user says test my agent
- Why did it call that tool
- It says the wrong thing when I ask X
- Test this change
Example prompts
- “test my agent”
- “try my agent”
- “does this work”
- “/debugging-livekit-agents”
What it can do on your machine
Read from SKILL.md and the folder at commit 76ddabb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Livekit Agents loads about 1.2k tokens when it runs. Until then it costs about 185 tokens; SKILL.md has 585 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from livekit-examples/agent-starter-python at commit 76ddabb, republished under its MIT licence (© livekit-examples). 585 words, ~1,208 tokens.
Download SKILL.mdSave it as
.claude/skills/debugging-livekit-agents/SKILL.md (or your agent's skills folder).- name
- debugging-livekit-agents
- description
- Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it behaves. Wraps `lk agent debugger`: start the agent in text mode, send turns, read the tool calls, handoffs, errors and logs behind each reply, and restart after an edit. It runs without audio or a LiveKit room at one LLM call per turn, so it is the preferred way for a coding agent to live-test during development, and the default when the user says "test" without naming unit tests or simulations.
- license
- MIT
- metadata.author
- livekit
Debugging a LiveKit agent live
lk agent debugger runs the user's agent locally as a background process in text mode and lets
you drive a conversation one turn at a time. It's built for coding agents: you play the user,
choose each next line based on the last reply, and inspect what the agent did in between.
Speech is off and nothing goes to a LiveKit room, so a turn costs only the agent's own LLM and tool calls. That's cheap enough to use constantly while building.
Before the first use, confirm the command exists and read its help:
lk agent debugger --helpThe help is thorough and is the source of truth for subcommands and flags, so this skill doesn't
restate them. If the command is missing, the installed CLI predates it. Tell the user to update
lk and use testing-livekit-agents until then. Don't guess at an older command's shape.
The loop
Start the agent, say user turns, inspect what happened, edit the code, restart, repeat, and stop when you're done. Roughly:
lk agent debugger start
lk agent debugger say "Hi, what can you do?"
lk agent debugger say "Book me a table for two tonight"
lk agent debugger stopEach say prints everything the agent did in response (tool calls with arguments and results,
handoffs, errors) followed by the reply. Between turns you can look at the agent's chat history, a
live event stream, the process logs, and status; --help lists the subcommands.
Restart after every code edit. A running session keeps the old code, and it's easy to lose time debugging behavior the file no longer has.
Debugging with it
- Read the tool calls as well as the reply. The reply shows what went wrong; the tool call and its arguments usually show why. A wrong argument points to the prompt or the tool description. No call at all usually means the tool description never says when to use it.
- Interleave the logs when a tool misbehaves. An option shows the agent's log lines under the turn they belong to, so a tool's traceback appears right below the sanitized error the user would have heard. That's the quickest way from symptom to cause.
- Check the agent's chat history instead of relying on your memory of the conversation. It records what the LLM saw, including instruction and tool changes across handoffs. When behavior seems impossible, the history usually shows the context isn't what you assumed.
- Reproduce before you fix, then re-run the same turns. Keep the sequence of
saylines that triggered the bug so you can compare before and after. - Drive whole conversations. Most bugs take several turns to show up: details collected early that get lost, a user changing their mind mid-flow, a handoff that drops context. A single turn won't find them.
- Script it if a program is deciding the turns. There's machine-readable output and meaningful
exit codes. Check
--helpfor the current format instead of assuming field names.
Show full SKILL.md (123 more words)Show less
When to use something else
| Situation | Use |
|---|---|
| You want to hear it, or hand the user something to try | lk agent console (mic and speakers, a human at the keyboard) |
| The same failure keeps coming back | A turn-level regression test (testing-livekit-agents) |
| You need whole-conversation outcomes graded at scale | Simulations (running-livekit-simulations) |
| The bug is about speech: turn-taking, interruptions, transcription | Audio simulations. The debugger is text-only and can't see these |
The debugger is for finding bugs interactively. Once you've found one, write a test for it so a later change can't reintroduce it unnoticed.
Related skills
- Building the agent:
building-livekit-agents - Pinning a found bug as a test:
testing-livekit-agents - Whole-conversation checks:
writing-livekit-scenarios,running-livekit-simulations - Production-only failures (worker processes, providers, shutdown):
operating-livekit-agents - CLI flags and API facts:
reading-livekit-docs
© livekit-examples, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/debugging-livekit-agents of livekit-examples/agent-starter-python.
Open the folder on GitHubat commit 76ddabb
Used in 2 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in livekit-examples/agent-starter-python, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Debugging Livekit Agents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Livekit Agents this skilllivekit-examples/agent-starter-python | 264 | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Adk Setupgoogle/adk-python | 22k | — | ~993 | Automated safety check: Notes | Apache-2.0 | |
| Flowfile Debugging PlaybookEdwardvaneechoud/Flowfile | 375 | — | ~6.3k | Automated safety check: Pass | MIT | |
| Chrome Devtools MCPmanagedcode/dotnet-skills | 486 | — | ~2.2k | Automated safety check: Pass | MIT | |
| GitHub Issue Bugfix WorkflowQwenLM/qwen-code | 28k | — | ~873 | Automated safety check: Pass | Apache-2.0 | |
| Verified Coding Workflowamd/gaia | 1.6k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Flowfile Debugging Playbook
Edwardvaneechoud/Flowfile
Symptom-to-cause triage playbook for Flowfile (core/worker/kernel/frontend/AI) — covers "no such table" DB cascades (two distinct causes), import-time Alembic migration corruption, silent…
Chrome Devtools MCP
managedcode/dotnet-skills
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.
GitHub Issue Bugfix Workflow
QwenLM/qwen-code
Fixes a bug from a GitHub issue by reproducing it first with a test-engineer subagent, then fixing, verifying, adding regression tests and reviewing the diff.
Verified Coding Workflow
amd/gaia
Guides safe code changes by finding the right file with grep or semantic search, reading before editing, reproducing bugs first, and proving a fix with a real test run.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
More from livekit-examples/agent-starter-python
Writing Livekit Scenarios
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
Reading Livekit Docs
livekit-examples/agent-starter-python
Looks 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.
Running Livekit Simulations
livekit-examples/agent-starter-python
Runs LiveKit agent simulations and acts on the results. An agent skill from livekit-examples/agent-starter-python.
Building Livekit Agents
livekit-examples/agent-starter-python
Builds voice and chat AI agents with LiveKit Agents and LiveKit Cloud.
Operating Livekit Agents
livekit-examples/agent-starter-python
Deploys 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…
Testing Livekit Agents
livekit-examples/agent-starter-python
Writes turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js).
Related
Categories
Questions about Debugging Livekit Agents
What does Debugging Livekit Agents do?
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Debugging Livekit Agents is an agent skill from livekit-examples/agent-starter-python. Drives a multi-turn conversation with a LiveKit agent running locally to see what it does.
When should I use Debugging Livekit Agents?
Debugging Livekit Agents fits situations like: the user says test my agent; why did it call that tool; it says the wrong thing when I ask X; test this change.
How do I install Debugging Livekit Agents in Claude Code?
Run `npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a claude-code`. Or copy the skill folder (.agents/skills/debugging-livekit-agents in livekit-examples/agent-starter-python) into .claude/skills/debugging-livekit-agents in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Livekit Agents in Codex?
Run `npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a codex`. Or copy the skill folder (.agents/skills/debugging-livekit-agents in livekit-examples/agent-starter-python) into .agents/skills/debugging-livekit-agents in your project. Codex loads it when a task matches its description.
Can I use Debugging Livekit Agents in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add livekit-examples/agent-starter-python --skill debugging-livekit-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-livekit-agents, .gemini/skills/debugging-livekit-agents, .github/skills/debugging-livekit-agents and .opencode/skills/debugging-livekit-agents in your project.
What does Debugging Livekit Agents need to run?
SKILL.md names no scripts, command-line tools or credentials: Debugging Livekit Agents is instructions for the agent only.
Does Debugging Livekit Agents access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Livekit Agents safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Livekit Agents use?
Debugging Livekit Agents is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debugging Livekit Agents use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugging Livekit Agents?
Skills that share tags, products or a category with Debugging Livekit Agents: Adk Setup (google/adk-python, 22k stars), Flowfile Debugging Playbook (Edwardvaneechoud/Flowfile, 375 stars), Chrome Devtools MCP (managedcode/dotnet-skills, 486 stars) and GitHub Issue Bugfix Workflow (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Livekit Agents?
livekit-examples (a GitHub organization) maintains it in livekit-examples/agent-starter-python, which has 264 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.
Source: livekit-examples/agent-starter-python on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.