zoom-video-sdk-web

Zoom Video SDK for Web - JavaScript/TypeScript integration for browser-based video sessions, real-time communication, screen sharing, recording, and live transcription

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/video-sdk/web/SKILL.md

Quality

Content

52%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 content is highly actionable with strong executable code and a clear lifecycle, but it suffers from heavy merge-induced duplication and a progressive-disclosure structure whose referenced files largely do not exist in the bundle. De-duplicating the merged halves and aligning references with the actual bundle would substantially improve it.

Suggestions

Collapse the duplicated merged halves into a single navigation index, Quick Start path, and Key Learnings/Quick Reference section to remove roughly half the document.

Reconcile references with the actual bundle: either restore the missing concepts/, examples/, troubleshooting/, and RUNBOOK.md files, or remove/inline the dead links so every referenced path resolves.

Move time-sensitive version details (v2.3.12, v1.11.2, "As of v1.11.2...") into a dedicated version/deprecation note so they do not pad the main guidance.

Dimension	Reasoning	Score
Conciseness	The ~810-line body is a merged duplicate of two SKILL.md files (line 591 "Merged from video-sdk/web/SKILL.md"), re-stating the Quick Start path, documentation library, Key Learnings, and Quick Reference twice, which is noticeably verbose with several unnecessary padded sections.	2 / 5
Actionability	Provides mostly executable, copy-paste-ready code for the common cases (init/join, video rendering, audio, screen share, chat, recording, error handling) plus a feature-client table, with only minor gaps such as the partial VideoProcessor example and reliance on referenced files for full details.	4 / 5
Workflow Clarity	The SDK lifecycle is given as an explicit ordered sequence (create → init → join → get stream → start media) with a "CRITICAL ORDER" section and wrong/right examples, plus error-handling recovery guidance; only minor validation checkpoints are missing from the main flow.	4 / 5
Progressive Disclosure	The body signals a rich one-level reference structure (concepts/, examples/, troubleshooting/, RUNBOOK.md) but the actual bundle contains only references/web-reference.md and references/events-reference.md, so the large majority of referenced paths are broken, and the navigation index is duplicated with confusing self-referential SKILL.md entries.	2 / 5
	Total	12 / 20 Passed

Description

66%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 specific and names a clear niche with good natural trigger terms, but it omits any explicit "Use when..." guidance, capping its completeness. Adding a trigger clause and a one-line disambiguation from the Meeting SDK would raise it notably.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when building custom browser-based video sessions with the Zoom Video SDK; for embedded Zoom meetings use the Meeting SDK instead."

Add a brief disambiguator (custom video sessions vs. embedded meetings) so it does not conflict with the sibling meeting-sdk/web skill.

Round out capability coverage with chat, command channel, and subsessions, or state the list is illustrative, to avoid implying the SDK is limited to the five named features.

Dimension	Reasoning	Score
Specificity	Names the domain ("Zoom Video SDK for Web") and lists several concrete capabilities ("browser-based video sessions, real-time communication, screen sharing, recording, and live transcription"), but these are SDK features rather than actions Claude performs and several body-documented capabilities (chat, command channel, subsessions, whiteboard) are absent, leaving minor coverage gaps.	4 / 5
Completeness	The "what" is clear ("JavaScript/TypeScript integration for browser-based video sessions..."), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("Zoom Video SDK", "screen sharing", "live transcription", "browser-based video sessions", "JavaScript/TypeScript") with good coverage, though a few natural variants are missing and no file-extension/SDK-package synonyms are present.	4 / 5
Distinctiveness Conflict Risk	"Zoom Video SDK for Web" names a clear, specific niche with minimal generic conflict, but it does not distinguish itself from the closely related meeting-sdk/web skill (which the body explicitly routes to), leaving minor overlap risk.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (815 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 60 missing, 4 suspicious	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/video-sdk/web/SKILL.md
Commit: 1e28582

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