Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
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.
Install Reading Livekit Docs
$ npx skills add livekit-examples/agent-starter-python --skill reading-livekit-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install livekit-examples/agent-starter-python reading-livekit-docs --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/reading-livekit-docs .claude/skills/reading-livekit-docs && 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 "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .claude/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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/reading-livekit-docsType 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 reading-livekit-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install livekit-examples/agent-starter-python reading-livekit-docs --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/reading-livekit-docs .agents/skills/reading-livekit-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .agents/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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 reading-livekit-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install livekit-examples/agent-starter-python reading-livekit-docs --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/reading-livekit-docs .cursor/skills/reading-livekit-docs && 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 "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .cursor/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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/reading-livekit-docs--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 reading-livekit-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install livekit-examples/agent-starter-python reading-livekit-docs --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/reading-livekit-docs .gemini/skills/reading-livekit-docs && 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 "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .gemini/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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 reading-livekit-docsInstalls 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 reading-livekit-docs -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/reading-livekit-docs .github/skills/reading-livekit-docs && 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 "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .github/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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 reading-livekit-docs -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 reading-livekit-docs --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/reading-livekit-docs .opencode/skills/reading-livekit-docs && 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 "reading-livekit-docs" agent skill from https://github.com/livekit-examples/agent-starter-python/tree/main/.agents/skills/reading-livekit-docs into .opencode/skills/reading-livekit-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reading-livekit-docs", 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
reading-livekit-docs- GitHub stars
- 264
- Used in
- 1 other repo
- Token cost
- ~1.1k tokens
- SKILL.md length
- 562 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- A question touches LiveKit specifics: does LiveKit support X
- SKILL.md covers Where to look, in order of…, How to research, Reporting what you found and When the docs are wrong, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- What changed in agents 1.8
What it does
Reading Livekit Docs is an agent skill from 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. 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…
Its SKILL.md is about 1.1k 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 Changelog and release notes and MCP servers. It works with Model Context Protocol. The repository describes itself as: A complete voice AI starter for LiveKit Agents with Python. The licence is MIT.
When your agent uses it
- 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
Example prompts
- “does LiveKit support X”
- “what changed in agents 1.8”
- “what are the arguments to Y”
- “/reading-livekit-docs”
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
Reading Livekit Docs loads about 1.1k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 562 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). 562 words, ~1,050 tokens.
Download SKILL.mdSave it as
.claude/skills/reading-livekit-docs/SKILL.md (or your agent's skills folder).- name
- reading-livekit-docs
- description
- 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.
- license
- MIT
- metadata.author
- livekit
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.
2. lk docs. Available wherever the LiveKit CLI is installed, with no MCP setup. Use it when
the MCP tools aren't there; don't stop to ask the user to install anything first. It can search the
docs, fetch pages, search code across LiveKit's repositories, show an SDK's recent changelog, report
pricing, and submit feedback. Start with:
lk docs --help
lk docs search "agent simulations"Once search has shown you the right page, fetch it. There's machine-readable output if you'd rather parse than read.
3. Web search against docs.livekit.io. Only when neither of the above is available. Tell the
user you fell back to it, and mark generated code as unverified.
How to research
- Search before you read. Search returns per-page excerpts, which is usually enough to pick the right page. Fetch full pages only once you know which one you need, or you'll fill the context window with pages you don't use.
- Use code search for how, docs for what. Docs tell you a parameter exists. LiveKit's own examples show how it's called. When a docs page and a working example disagree, go with the example and mention the discrepancy.
- Use the changelog for version questions. "Is X available yet", "when did Y change", and "why doesn't this argument exist" are answered by the changelog, not search.
- Check the version you're on. The installed SDK and CLI determine what works, and a documented
feature may not exist in the installed version. For any CLI command,
--helpon the installed binary outranks every other source.
Show full SKILL.md (212 more words)Show less
Reporting what you found
- Cite the page when a decision rests on it, so the user can check you.
- Say when you couldn't verify something. "I could not confirm this signature against the docs" is useful to the user. A silent guess isn't.
- Mark unverified code. If you had to write LiveKit code without a lookup, add a comment at the call site saying it's unverified, and say so in your reply.
- Don't invent a flag or parameter to make an example look complete. An incomplete example with a note is better than a plausible fabrication.
When the docs are wrong
Sometimes a page contradicts the SDK source or the CLI's --help. When that happens:
- Go with what runs.
--help, the installed SDK's source, and a working example outrank a prose page. Tell the user which one you followed and why. - Report it with the docs feedback command, and tell the user you did, so the next person doesn't hit the same error.
lk docs sometimes warns about version skew when the docs server is a little ahead of the CLI.
That's routine and the results are still good. Suggest updating lk and keep going.
Related skills
- Building an agent:
building-livekit-agents - Live-testing one during development:
debugging-livekit-agents - Unit tests:
testing-livekit-agents - Simulations:
writing-livekit-scenarios,running-livekit-simulations
© 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/reading-livekit-docs 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
Reading Livekit Docs 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 |
|---|---|---|---|---|---|---|
| Reading Livekit Docs this skilllivekit-examples/agent-starter-python | 264 | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Trello Releasedelorenj/mcp-server-trello | 446 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Githits Releasegithits-com/githits-cli | 114 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Suede Launch PackagingJasonColapietro/suede-creator-skills | 127 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Release Prepjohnhuang316/code-index-mcp | 1k | — | ~680 | Automated safety check: Pass | MIT |
Similar skills
MCP Server Trello Release
delorenj/mcp-server-trello
Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.
Githits Release
githits-com/githits-cli
A skill your agent uses when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release.
Suede Launch Packaging
JasonColapietro/suede-creator-skills
Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.
Release Prep
johnhuang316/code-index-mcp
A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.
MCP Apps Sync Docs
apollographql/apollo-mcp-server
Syncs MCP Apps documentation with the @apollo/client-ai-apps changelog.
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.
Debugging Livekit Agents
livekit-examples/agent-starter-python
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does.
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
Works with
Categories
Questions about Reading Livekit Docs
What does Reading Livekit Docs do?
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. Reading Livekit Docs is an agent skill from 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.
When should I use Reading Livekit Docs?
Reading Livekit Docs fits situations like: 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.
How do I install Reading Livekit Docs in Claude Code?
Run `npx skills add livekit-examples/agent-starter-python --skill reading-livekit-docs -a claude-code`. Or copy the skill folder (.agents/skills/reading-livekit-docs in livekit-examples/agent-starter-python) into .claude/skills/reading-livekit-docs in your project. Claude Code loads it when a task matches its description.
How do I install Reading Livekit Docs in Codex?
Run `npx skills add livekit-examples/agent-starter-python --skill reading-livekit-docs -a codex`. Or copy the skill folder (.agents/skills/reading-livekit-docs in livekit-examples/agent-starter-python) into .agents/skills/reading-livekit-docs in your project. Codex loads it when a task matches its description.
Can I use Reading Livekit Docs 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 reading-livekit-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reading-livekit-docs, .gemini/skills/reading-livekit-docs, .github/skills/reading-livekit-docs and .opencode/skills/reading-livekit-docs in your project.
What does Reading Livekit Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Reading Livekit Docs is instructions for the agent only.
Does Reading Livekit Docs 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 Reading Livekit Docs 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 Reading Livekit Docs use?
Reading Livekit Docs 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 Reading Livekit Docs use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Reading Livekit Docs?
Skills that share tags, products or a category with Reading Livekit Docs: Release (PrefectHQ/fastmcp, 28k stars), MCP Server Trello Release (delorenj/mcp-server-trello, 446 stars), Githits Release (githits-com/githits-cli, 114 stars) and Suede Launch Packaging (JasonColapietro/suede-creator-skills, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Reading Livekit Docs?
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.