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

80%

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

77%Weight 40%Scale 1-3

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

Highly actionable with a clearly sequenced, emphasized lifecycle, but undermined by duplicated merged-document content and a monolithic structure whose primary navigation points to bundle files that are largely missing.

Suggestions

Remove the duplicated "Merged from video-sdk/web/SKILL.md" navigation/index section — it repeats Quick Start Path, Documentation Structure, Key Learnings, and Quick Reference already covered above.

Either create the referenced bundle files (concepts/sdk-architecture-pattern.md, examples/*.md, troubleshooting/common-issues.md) or stop linking to them; currently most navigation targets 404 within the bundle.

Move the large inline reference material (Feature Clients table, browser-compatibility matrix, full code samples for every feature) into the existing references/ files to slim SKILL.md into a true overview.

Dimension	Reasoning	Score
Conciseness	Individual sections are SDK-specific and efficient, but the body is padded: a "Merged from video-sdk/web/SKILL.md" section repeats the Quick Start Path, Documentation Structure, Key Learnings, and Quick Reference, and the getMediaStream-after-join warning appears 3+ times. Mostly efficient but could be tightened significantly.	2 / 3
Actionability	Abundant copy-paste-ready executable code with specific methods (createClient, init, join, attachVideo, getChatClient) and concrete enums/error tables — fully actionable, not pseudocode.	3 / 3
Workflow Clarity	The SDK Lifecycle is given as an explicit, numbered "CRITICAL ORDER" sequence (create → init → join → getStream → startMedia) with WRONG/CORRECT contrasts and a join error-handling table providing a recovery loop.	3 / 3
Progressive Disclosure	References are signaled, but the body is a ~800-line monolith with content that should live in separate files inline, and most referenced bundle paths (concepts/, examples/, troubleshooting/common-issues.md) do not exist in the bundle — only references/ is present.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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

A specific, third-person description with strong natural trigger terms and a clear niche. Its main weakness is the absence of an explicit "Use when…" trigger clause, which caps completeness at 2.

Suggestions

Append an explicit trigger clause, e.g. "Use when building browser-based Zoom Video SDK apps, custom video sessions, or Web video/audio integration."

Add the SDK version target (e.g. "v2.3.x") so the description signals recency without relying on the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "browser-based video sessions, real-time communication, screen sharing, recording, and live transcription" — matching the multi-action anchor rather than vague language.	3 / 3
Completeness	It clearly answers "what" the skill does, but there is no "Use when…" clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered ("Zoom Video SDK", "Web", "video sessions", "screen sharing", "recording", "live transcription"), the kind of phrasing a user would actually say.	3 / 3
Distinctiveness Conflict Risk	"Zoom Video SDK for Web" carves out a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 11c74d6

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