# Reading Livekit Docs

Looks up current LiveKit facts (API signatures, CLI flags, config options, model and...

- Repository: https://github.com/fcakyon/claude-codex-settings (1195 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add fcakyon/claude-codex-settings --skill reading-livekit-docs -g -a claude-code -y`
Codex: `npx skills add fcakyon/claude-codex-settings --skill reading-livekit-docs -g -a codex -y`
Cursor: `npx skills add fcakyon/claude-codex-settings --skill reading-livekit-docs -g -a cursor -y`
Gemini CLI: `npx skills add fcakyon/claude-codex-settings --skill reading-livekit-docs -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add fcakyon/claude-codex-settings`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

```bash
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

The rest: https://github.com/fcakyon/claude-codex-settings/blob/HEAD/plugins/livekit-skills/skills/reading-livekit-docs/SKILL.md