CtrlK
BlogDocsLog inGet started
Tessl Logo

build-zoom-video-sdk-app

Use when using Video SDK.

47

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/video-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 is an exemplary lean router — concise, correctly sequenced, with sensible ordering gates and good Meeting SDK disambiguation. Its main weaknesses are that the workflow tells what to do but not how (without linking the reference files that contain the how), and the reference list is half-broken against the actual bundle.

Suggestions

Fix the broken reference paths: web/SKILL.md, android/SKILL.md, ios/SKILL.md, windows/SKILL.md, and linux/SKILL.md do not exist in this bundle, and ../ui-toolkit/SKILL.md escapes the skill directory — the local references/ui-toolkit.md should be linked instead.

Link the 8 orphaned reference files from SKILL.md — particularly references/authorization.md (token generation, directly relevant to step 3), references/token-contract-test-spec.md, and references/troubleshooting.md (relevant to step 6) — so the bundle's actual content is discoverable.

Add at least one concrete pointer or snippet in the workflow (e.g. where token generation code lives or the required token fields) so step 3 is executable rather than purely directive.

DimensionReasoningScore

Conciseness

The 28-line body is lean with zero padding: no explanation of what Video SDK is, no library background, and a routing sentence that earns its tokens. Matches anchor 5 ('every token earns its place').

5 / 5

Actionability

Steps name concrete features ('audio/video publish-subscribe, screen share, chat') and concrete debug dimensions, but no code, commands, or pointers for how to execute them — e.g. step 3 says 'generate Video SDK session tokens server-side' yet never links references/authorization.md, which already exists in the bundle. Anchor 3: some concrete guidance but incomplete.

3 / 5

Workflow Clarity

A clear 6-step sequence with ordering gates ('Implement join... before advanced media features', 'only after the session lifecycle is stable') and a fit-confirmation first step; checkpoints are implicit rather than explicit verify steps, so anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The references section is well-labeled, but scored against the actual bundle: 6 of 8 links (web/, android/, ios/, windows/, linux/SKILL.md, and ../ui-toolkit/SKILL.md which escapes the skill directory) point to nonexistent paths, while 8 of the 10 files in references/ (authorization.md, token-contract-test-spec.md, troubleshooting.md, triage-intake.md, forum-top-questions.md, environment-variables.md, licensing-and-entitlements.md, ui-toolkit.md) are never referenced and are undiscoverable. Navigation to the real bundle content is broken, matching anchor 3 rather than anchor 4's 'minor organization gaps'.

3 / 5

Total

15

/

20

Passed

Description

28%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 is a bare, circular trigger clause: it says when to use the skill but never says what the skill does, offers only a single product-name keyword, and leaves the Video SDK vs Meeting SDK distinction entirely to the body. It is closer to the 'bad overall' examples than the good ones.

Suggestions

Add a 'what' clause naming the skill's concrete capabilities, e.g. 'Build custom video sessions with the Zoom Video SDK: join/leave lifecycle, audio/video publish-subscribe, screen share, and chat across web, mobile, and native platforms.'

Expand trigger terms beyond the single product name to natural user phrases such as 'custom video session', 'embedded video call', or 'Zoom Video SDK'.

Include a disambiguation hint in the description (e.g. 'Use for custom app-owned video sessions, not regular Zoom meetings — route those to Meeting SDK') to reduce wrong-skill triggering.

DimensionReasoningScore

Specificity

"Use when using Video SDK." names the domain (Video SDK) but states zero actions — not even generic ones — so it matches 'names the domain but actions are minimal or generic' rather than anchor 1's pure abstraction or anchor 3's 1-2 concrete actions.

2 / 5

Completeness

Only the 'when' is present with no 'what' — exactly anchor 2's pattern ('Use when working with documents'). Anchor 3 requires a clear 'what', which is entirely absent.

2 / 5

Trigger Term Quality

The only keyword is the product name "Video SDK"; natural user phrases like "custom video session", "embedded video", or "Zoom video" are missing, and the trigger is circular ("use when using"). This is slightly below anchor 3's 'some relevant keywords but missing common variations'.

2 / 5

Distinctiveness Conflict Risk

"Video SDK" is the exact product name, but the description does nothing to disambiguate from the closely related Meeting SDK — a confusion the skill body itself explicitly addresses — so anchor 3 ('somewhat specific but could still overlap with similar skills') fits better than anchor 4.

3 / 5

Total

9

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

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.