CtrlK
BlogDocsLog inGet started
Tessl Logo

zoom-video-sdk-windows

Zoom Video SDK for Windows - C++ integration for video sessions, raw audio/video capture, screen sharing, recording, and real-time communication

49

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

50%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 rich with executable, copy-paste-ready C++ guidance and well-marked critical gotchas, but it is materially over-long due to a duplicated navigation/index section and re-explained basics, and it references roughly two dozen bundle paths that do not exist. Trimming the duplicate block and either supplying or removing the dead links would markedly improve quality.

Suggestions

Delete the duplicated 'Merged from video-sdk/windows/SKILL.md' block (Documentation Structure, By Use Case, Most Critical Documents, Key Learnings, Quick Reference) since the same navigation already appears in the Quick Links and Documentation Library sections.

Resolve the ~25 dead links: either create the referenced concepts/examples/troubleshooting files in the bundle, or remove/collapse those links so progressive disclosure reflects the actual bundle structure (only references/ currently exists).

Add explicit validation checkpoints to the session-join and subscribe workflows (e.g., 'Verify joinSession returned non-null and onSessionJoin fired before subscribing to video') to convert the implicit sequence into a true feedback-loop workflow.

DimensionReasoningScore

Conciseness

The ~1000-line body is noticeably verbose: it re-explains SDK basics and contains a large duplicated block ('Merged from video-sdk/windows/SKILL.md') that repeats the documentation index, By-Use-Case list, Most Critical Documents, Key Learnings, and Quick Reference already covered earlier. Not a 1 because the core guidance is accurate and code-focused, but the redundancy and padding are substantial.

2 / 5

Actionability

Provides concrete, copy-paste-ready C++ for initialization, session join, message pump, Canvas/raw-data rendering, YUV420->RGB conversion, and event-driven subscription; minor gaps (e.g., C# snippet is skeletal, JWT generation is referenced elsewhere) keep it just below fully executable anchor 5.

4 / 5

Workflow Clarity

Quick Start and Critical Gotchas give a recognizable numbered sequence with CRITICAL markers, but validation/checkpoint steps are implicit rather than explicit feedback loops (no 'verify join succeeded, then proceed' gates), so the sequence is present but checkpoints are missing.

3 / 5

Progressive Disclosure

References are extensively signaled (Quick Links, Documentation Library), but only references/*.md actually exist in the bundle while ~25 links into concepts/, examples/, troubleshooting/, and dotnet-winforms/ point to missing files, and large indexes are duplicated inline rather than cleanly split; some structure exists but organization is inconsistent with dead links.

3 / 5

Total

12

/

20

Passed

Description

58%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 clearly states what the skill covers with a strong, specific capability list in third person, but omits any explicit 'Use when...' trigger guidance and relies on technical jargon over natural user phrasing. It is mostly distinct but would benefit from trigger phrases and synonyms.

Suggestions

Append an explicit trigger clause, e.g. 'Use when integrating the Zoom Video SDK on Windows for custom video apps, raw media capture/injection, recording, or live streaming.'

Add natural synonyms users actually say ('Zoom', 'join a video session', 'video call', 'live captions') rather than only technical jargon like 'C++ integration' and 'real-time communication'.

Lead with the action verbs ('Join video sessions, capture raw audio/video frames, share screens, record, and stream') to lift specificity toward the comprehensive anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions ('video sessions, raw audio/video capture, screen sharing, recording, and real-time communication'), giving broad coverage; falls just short of anchor 5 because the framing 'C++ integration for ...' is slightly generic rather than enumerating each capability as a distinct verb.

4 / 5

Completeness

Has a clear 'what' (the enumerated capabilities) but provides no 'when'/'Use when...' trigger clause; per the rubric guideline a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain terms ('raw audio/video capture', 'screen sharing', 'recording') but leans on technical jargon and omits the natural phrases a user would actually say ('Zoom', 'join a video session', 'video call') and any file extension, so it has keyword coverage but missing common variations.

3 / 5

Distinctiveness Conflict Risk

'Zoom Video SDK for Windows' names a clear niche with distinct triggers and minimal overlap risk with other skills; not a 5 only because the capability list is generic enough to mildly overlap with general WebRTC/streaming skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1013 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 114 missing, 31 deeper-than-1-level

Warning

Total

14

/

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.