Skip to content

Install the current LiveKit agent skills - #108

Merged
bcherry merged 1 commit into
mainfrom
bcherry/update-agent-skills
Sep 25, 2026
Merged

bcherry merged 1 commit into
mainfrom
bcherry/update-agent-skills

Conversation

@bcherry

@bcherry bcherry commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

What

Replaces the bundled livekit-agents skill with the seven skills now in livekit/agent-skills (at 5d7488b):

  • reading-livekit-docs
  • building-livekit-agents
  • debugging-livekit-agents
  • testing-livekit-agents
  • writing-livekit-scenarios
  • running-livekit-simulations
  • operating-livekit-agents

Installed with npx skills add livekit/agent-skills --agent claude-code codex --skill '*' --copy, which writes each skill to both .claude/skills/ and .agents/skills/ (the layout this repo already used) and adds skills-lock.json, so npx skills update can refresh them later. Both copies are byte-identical to upstream.

Why

The bundled livekit-agents skill is the pre-split version, since replaced upstream by these focused skills (livekit/agent-skills#10). Left as is, it steers coding agents toward superseded guidance, such as a lk agent simulate form that now just prints help. Skill installation is moving into the LiveKit CLI, but until that ships, the starter should carry the current skills.

Notes for reviewers

  • Merge this before Remove the bundled LiveKit agent skills #106, which is now stacked on it and removes these skills once the CLI install lands.
  • The skill files are copied verbatim, so they're easiest to review upstream rather than here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01U7yszNU7t5aCHJsKLmU4hv


Generated by Claude Code

Replace the pre-split livekit-agents skill with the seven skills now in
livekit/agent-skills (at 5d7488b), installed with
`npx skills add livekit/agent-skills --agent claude-code codex --copy`.
That writes each skill to .claude/skills/ and .agents/skills/, and
records their sources and hashes in skills-lock.json so
`npx skills update` can refresh them.

This keeps the starter's skills current until the LiveKit CLI installs
them itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U7yszNU7t5aCHJsKLmU4hv

@u9g u9g left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I started reviewing the skills before realizing that this was just the entire skill repo

@@ -0,0 +1,134 @@
# State, effects, and evidence

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure that this shouldn't just go into the docs website?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+ should we make a postinstall script in package.json that just installs lk skills globally, so they don't need to live here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@u9g this is just temporary. the new version of the lk CLI will auto-prompt to install skills when using lk agent init and then we can pull these out of the repo


## Evidence comes from the boundary

Completion needs evidence from where it actually happens: a committed write, a delivered

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Completion needs evidence from where it actually happens: a committed write, a delivered
Action completion needs evidence from where it actually happens: a committed write, a delivered

## Evidence comes from the boundary

Completion needs evidence from where it actually happens: a committed write, a delivered
utterance, a runtime lifecycle event. An instruction to do something, a tool that returned a string,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why would a tool that returned a strong or a boolean named after the action not be evidence?


Keep one authoritative state object per session, supplied through the SDK's per-session user
data. Keep model-supplied facts separate from trusted identity, the clock, message and record ids,
and operation receipts. Don't recover missing state from a global "last session" variable, and

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't recover missing state from a global "last session" variable

This feels like something current agents wouldn't do. Not a removal suggestion, just a thought

Keep one authoritative state object per session, supplied through the SDK's per-session user
data. Keep model-supplied facts separate from trusted identity, the clock, message and record ids,
and operation receipts. Don't recover missing state from a global "last session" variable, and
don't manufacture a successful snapshot at export time.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and don't manufacture a successful snapshot at export time.

I don't know what this means

| "No, that's everyone" | Confirm the collection as recorded | Every existing entry and field |
| "No note for that one" | Record explicit absence on one entry | Its identity, title, all other entries |
| "Actually I'm not sure about that" | Retract one fact to unknown | The entry and unrelated facts |
| "It's spelled Okafor" | Change one identified entry's field | Its identity, other fields, other entries |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for this table, maybe something about asking for more info if something seems confusing?

Comment thread skills-lock.json
@@ -0,0 +1,47 @@
{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably we don't need a lock file

@bcherry

bcherry commented Sep 25, 2026

Copy link
Copy Markdown
Contributor Author

@u9g thanks for the feedback on the skills, i may improve them in the skills repo. gonna merge this as-is just to get it moving, we'll remove these from the repo once the CLI update ships

@bcherry
bcherry merged commit ec22151 into main Sep 25, 2026
5 checks passed
@bcherry
bcherry deleted the bcherry/update-agent-skills branch September 25, 2026 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants