Individual skill
reading-livekit-docs
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. 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.
plugins/livekit-skills/skills/reading-livekit-docs/SKILL.md
Source commit 4f2b4bc9a74024397b4688cbafd1ae538a83a5fb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,200
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- github Repository topic
- commit-message Repository topic
- pull-requests Repository topic
- cursor Repository topic
- gemini-cli Repository topic
- codex Repository topic
- codex-cli Repository topic
- plugin Repository topic
- ai-agents Repository topic
- writing Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Reading LiveKit documentation
LiveKit's SDKs change faster than model training data, so anything you remember about a LiveKit
API, CLI flag, or default is a guess. Wrong guesses cost time: a wrong flag wastes a run, a wrong
signature wastes a build.
**Every LiveKit-specific fact you state or put in code should come from a lookup in this
session.** That includes facts you're confident about and patterns you've seen in other repos.
## Where to look, in order of preference
**1. The LiveKit Docs MCP server.** If its tools are in your session, use them. They're the same
source the CLI uses, with less friction.
