build-zoom-meeting-sdk-app

Use when using Meeting SDK.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The body is a lean, well-sequenced orchestration overview with an explicit validation step and debug loop, but it provides no executable code and five of its eight referenced sub-skill files are missing, harming navigation.

Suggestions

Create or restore the missing referenced files (web/SKILL.md, android/SKILL.md, ios/SKILL.md, windows/SKILL.md, linux/SKILL.md), or remove the broken links.

Add a minimal executable snippet (e.g., a signature-generation or join call) or a copy-paste command so the body is actionable on its own.

Verify every path in the References list resolves to a real bundle file so navigation is unbroken.

Dimension	Reasoning	Score
Conciseness	The ~24-line body is dense with concrete specifics, has no padding, and does not explain concepts Claude already knows; the intro, workflow, and references all earn their tokens.	3 / 3
Actionability	The guidance is concrete (names ZAK, meeting number, SDK signature, role, and platform list) but offers no executable code, commands, or copy-paste examples, deferring actual execution to referenced files, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The 5-step sequence is clearly ordered with an explicit validation checkpoint (step 3) and a debug/error-recovery feedback loop (step 5), plus a troubleshooting reference, matching the score-3 anchor.	3 / 3
Progressive Disclosure	The overview is lean and references are one level deep and well signaled, but 5 of the 8 referenced paths (web/SKILL.md, android/SKILL.md, ios/SKILL.md, windows/SKILL.md, linux/SKILL.md) do not exist, breaking navigation and preventing the 'easy navigation' bar of 3.	2 / 3
	Total	10 / 12 Passed

Description

40%

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 single thin trigger clause with an explicit 'when' but no statement of what the skill does. It is specific enough to its niche yet risks overlap with the sibling Video SDK skill.

Suggestions

Add concrete actions to the description, e.g. 'Join, start, and embed real Zoom meetings via the Meeting SDK. Use when building apps that join or host Zoom meetings.'

Include natural user variations beyond the technical term, such as 'Zoom meeting', 'embed Zoom', and 'join/host a Zoom meeting'.

Disambiguate from the Video SDK skill directly in the description, e.g. 'for real Zoom meetings (not custom video sessions)'.

Dimension	Reasoning	Score
Specificity	The description 'Use when using Meeting SDK.' names only a domain, not any concrete actions (no 'join', 'start', or 'embed' verbs), matching the score-1 anchor for vague or absent actions.	1 / 3
Completeness	It has an explicit 'Use when' trigger (the 'when'), but the 'what' is only weakly implied rather than stated, so it does not reach the both-what-and-when bar of 3 yet stays above 1 because the trigger is explicit and clear.	2 / 3
Trigger Term Quality	'Meeting SDK' is a relevant keyword a developer would say, but it is a single technical term missing common variations like 'Zoom meeting', 'embed Zoom', or 'join meeting', fitting the score-2 anchor of some relevant keywords but missing variations.	2 / 3
Distinctiveness Conflict Risk	'Meeting SDK' is a specific product niche, but a near-twin sibling skill (build-zoom-video-sdk-app) means a user saying 'Zoom SDK' could trigger the wrong skill, fitting 'somewhat specific but could still overlap with similar skills'.	2 / 3
	Total	7 / 12 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
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/meeting-sdk/SKILL.md
Commit: 11c74d6

Reviewed: about 8 hours 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.