Name: livekit
Rating: 56.8 (1 reviews)
Author: membranedev

livekit

LiveKit integration. Manage data, records, and automate workflows. Use when the user wants to interact with LiveKit data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/livekit/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers executable membrane CLI commands and a clear connection workflow with state-driven polling, but lacks explicit validation/verification checkpoints around action runs and proxy requests. It is well-structured and reasonably concise for a self-contained skill with no bundle files.

Suggestions

Add explicit verification checkpoints after running actions (e.g., inspect the output field / error before proceeding) to support the workflow clarity feedback loop.

Trim the opening LiveKit overview paragraph and the best-practices prose that restates guidance already implied by the command examples.

Clarify the numbered step sequence (Step 1 / Step 2) consistently, since the flow references 'Step 2' but only labels '1b'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal concept explanation, though the LiveKit overview paragraph and some explanatory prose (e.g., 'This will burn less tokens') could be trimmed, fitting the score-4 anchor of efficient with minor over-explanation.	4 / 5
Actionability	It provides concrete, copy-pasteable membrane CLI commands with flags and JSON examples covering the common connection and action cases, with only minor gaps such as absent example outputs for some commands, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connect-and-poll sequence is laid out with state transitions and a polling loop, but there are no explicit validation checkpoints after running actions or verifying readiness before proceeding, and the destructive/batch-capable proxy path lacks verification, capping at 3 per the validation guideline.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Actions, Best practices) with no bundle files present and no nested references; minor gaps are that some reference-style detail (the proxy flag table) is inline rather than separated, fitting the score-4 anchor for a self-contained skill.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the LiveKit niche and includes an explicit Use-when trigger, but its actions are generic and not specific to LiveKit's audio/video capabilities. Stronger trigger terms and concrete capabilities would raise specificity and trigger-term quality.

Suggestions

Replace generic actions with LiveKit-specific capabilities (e.g., 'Manage rooms, participants, and audio/video tracks') to improve specificity.

Add natural trigger phrases users would say, such as video conferencing, live streaming, real-time audio/video, or LiveKit rooms.

Expand the 'Use when' clause with concrete trigger conditions like joining/creating rooms or managing participants.

Dimension	Reasoning	Score
Specificity	Names the domain (LiveKit) and two generic actions ("manage data, records, and automate workflows"), but the actions are abstract and not LiveKit-specific, matching the score-3 anchor of naming the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It has a clear "what" (LiveKit integration to manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with LiveKit data"), though the "when" could be more specific with concrete trigger phrases, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	"interact with LiveKit data" provides a relevant keyword but misses common user phrasings like audio/video calls, rooms, conferencing, or streaming; coverage of natural terms is partial per the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The LiveKit niche is fairly distinct and unlikely to trigger for unrelated skills, though "manage data, records, and automate workflows" is generic enough to risk minor overlap with broad automation skills, matching the score-4 anchor of mostly distinct with minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/livekit/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.