writing-livekit-scenarios SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
writing-livekit-scenarios from fcakyon/claude-codex-settings is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fcakyon/claude-codex-settings/writing-livekit-scenarios@git:20261001.f7836daPins git:20261001.f7836da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fcakyon/claude-codex-settings
- Path
plugins/livekit-skills/skills/writing-livekit-scenarios/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261001.f7836da, committed Oct 1, 2026
- Size
- 10,046 bytes
- Repository stars
- 1,200
- License
- Apache-2.0
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my real database", "seed state per scenario", "it passed but booked the wrong thing", "grade the final state", or wants to stress-test a flow before shipping. Covers generating a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Writing simulation scenarios A scenario is a simulated user's **`instructions`** (who they are, what they want) plus **`agent_expectations`** (what counts as success). A simulation plays the scenario against the real agent, and an LLM judge grades the transcript. Runs are disposable. The scenario file is what lasts: it gets reviewed in diffs, re-run for years, and it's what catches a prompt edit that breaks something without anyone noticing. Before writing a file, look up the exact schema and CLI flags with `reading-livekit-docs`. Field names and commands change, so this skill doesn't restate them. Conceptually, a file is a named group of scenarios. Each scenario has the simulated user's instructions, the pass criteria, and optionally tags for grouping and per-scenario data the agent can read at runtime. If the CLI offers to add stable per-scenario ids to a file, accept and commit them. ## Start from a generated baseline Don't start from an empty file. LiveKit's generator reads the agent's source and produces a decent first pass much faster than you'd write ten scenarios by hand: ```bash lk agent simulate text -n 10 # confirm the exact flags with --help ``` …
Read the whole file at its exact version.
How to install
mdr add fcakyon/claude-codex-settings/writing-livekit-scenarios@sha256:6660d0790031a6caThe line at the top of this page pins the label git:20261001.f7836da, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t22lipdzkc5ndpeb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 1, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10046 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fcakyon/claude-codex-settings · 1,200 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t22lipdzkc5ndpeb GET https://markdownregistry.com/api/v1/resolve?ref=fcakyon/claude-codex-settings/writing-livekit-scenarios GET https://markdownregistry.com/api/v1/blob/6660d0790031a6ca6b08f833878f29a7648710baeec180a1f1e9b34e275e56d7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from fcakyon/claude-codex-settings
Every file in fcakyon/claude-codex-settings