Name: video-sdk
Rating: 53.6 (1 reviews)
Author: membranedev

video-sdk

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

Quality

60%

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/video-sdk/SKILL.md

Quality

Content

63%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 strong executable guidance and a reasonably clear workflow with a connection-state feedback loop, but it opens with unnecessary concept explanation and keeps reference material inline rather than splitting it into separate files. It is solidly usable with moderate trimming and restructuring gains available.

Suggestions

Remove or condense the opening paragraph explaining what a video SDK is; Claude already knows this and it adds tokens without actionable value.

Move the proxy request flag reference table and the clientAction state schema into a separate reference file linked from the body to improve progressive disclosure.

Either populate the 'Popular actions' section with named common actions or remove the empty header so it does not promise content it does not deliver.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening three-sentence explanation of what a video SDK is ('A video SDK allows developers to embed video conferencing...') restates a concept Claude already knows and could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready membrane CLI commands for auth, connection, action search/run, and proxying, with minor gaps such as the 'Popular actions' section that only repeats the search command without listing actual actions.	4 / 5
Workflow Clarity	There is a clear install -> auth -> connect -> search -> run -> proxy sequence with a feedback loop for connection readiness (polling state and re-polling after CLIENT_ACTION_REQUIRED), though validation after running actions or proxy requests is absent.	4 / 5
Progressive Disclosure	The body is well-sectioned with headers but all content lives inline in one file with no bundle/reference files, and reference-like material (the proxy flag table, the clientAction schema) that could be split out is inlined.	3 / 5
	Total	14 / 20 Passed

Description

57%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 has an explicit 'Use when' trigger and a distinctive product-specific name, but its capability verbs are generic rather than concrete and it lacks natural trigger synonyms. It is functional but would benefit from sharper, more specific action language.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Video SDK actions such as 'create and join video rooms, manage participants, and start/stop recordings'.

Add natural user trigger phrases like 'video conferencing', 'video calls', or 'video streaming' alongside 'Video sdk' so the skill surfaces for real-world phrasings.

Tighten the 'Use when' clause to name specific intents (e.g., 'Use when the user wants to embed video calls, manage room participants, or trigger recordings via Video sdk').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Video sdk integration') but its actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Video sdk data'); the when is explicit, though the what is vague, matching the 'has both what and when; when could be more explicit or specific' anchor.	4 / 5
Trigger Term Quality	It repeats 'Video sdk' / 'Video sdk data' as triggers but omits natural variations a user would actually say (video conferencing, video calls, streaming), fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The product-specific 'Video sdk' naming carves a clear niche with minimal conflict risk, though the generic action verbs ('manage data, records, automate workflows') leave minor overlap with general data-management skills.	4 / 5
	Total	13 / 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/video-sdk/SKILL.md
Commit: f484c82

Reviewed: 3 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.