zoom-meeting-sdk-web-component-view

Zoom Meeting SDK Web - Component View. Embeddable Zoom meeting components with Promise-based API for flexible integration. Ideal for React/Vue/Angular apps and custom layouts. Uses ZoomMtgEmbedded with async/await patterns and embeddable UI containers.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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 content is highly actionable with complete, executable examples and a clearly sequenced init flow, but it inlines a large API reference that belongs in separate reference files and carries console.log padding across event examples. Progressive disclosure is the weakest dimension because the reference layer is thin and one referenced file is missing.

Suggestions

Move the full event-listener and method catalogs into a dedicated reference file (e.g. `references/api.md`) and keep only key examples inline in SKILL.md to improve progressive disclosure.

Strip the repetitive `console.log` lines from event examples so each snippet shows only the meaningful payload handling.

Either add the referenced `RUNBOOK.md` to the bundle or remove the link to avoid a broken one-level-deep reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but every event example carries `console.log` padding and a large API reference (all events, methods, and init options) is inlined rather than trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready code covers the common cases: the complete init/join flow, method calls, a full React component, and a concrete error-handling switch on `error.reason`.	5 / 5
Workflow Clarity	The initialization flow is explicitly numbered (Step 1-4) with try/catch error handling and a React pattern that tracks `isJoined` via the `connection-change` event as a verification checkpoint, though no standalone preflight validation step is inlined (it is deferred to RUNBOOK.md).	4 / 5
Progressive Disclosure	Section structure exists and a reference index (`references/index.md`, verified present) is linked, but the bulk of the API reference is inlined in SKILL.md and `RUNBOOK.md` is referenced but not present in the bundle, so organization is only partially split.	3 / 5
	Total	15 / 20 Passed

Description

61%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 distinguishable, naming the API object and integration style, but lacks an explicit 'Use when...' trigger clause and concrete user-facing actions, capping completeness and specificity at the midpoint. It reads as a capable overview rather than a fully triggered routing description.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when embedding a real Zoom meeting with a custom UI in a web app, not for Video SDK custom sessions'.

Surface 1-2 concrete actions in the description (e.g. 'createClient, init, and join meetings') to lift specificity from 3 to 4-5.

Include the most common user phrasings (e.g. 'embed Zoom', 'Zoom web SDK', 'webinar') as natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain, the API object (`ZoomMtgEmbedded`), and concrete patterns (Promise-based API, async/await, embeddable UI containers), but lists no concrete user-facing actions like createClient/init/join, so it stops at '1-2 concrete actions'.	3 / 5
Completeness	Has a clear 'what' (embeddable meeting components with Promise-based API) but only a weakly implied 'when' via 'Ideal for React/Vue/Angular apps and custom layouts'; the missing explicit 'Use when...' trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage including 'Zoom Meeting SDK', 'Component View', and framework names 'React/Vue/Angular' that users would actually say, though a few natural synonyms (e.g. 'embed video', 'webinar') are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Component View' label and `ZoomMtgEmbedded` API object clearly distinguish it from the Client View (`ZoomMtg`) and Video SDK skills, leaving only minor overlap risk with the closely related Client View skill.	4 / 5
	Total	14 / 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 (610 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing, 4 suspicious	Warning

	Total	14 / 16 Passed

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

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