setup-zoom-websockets

Use when building Zoom WebSockets.

1.53x

Quality

57%

Does it follow best practices?

Impact

100%

1.53x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/websockets/SKILL.md

Quality

Content

75%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 a well-organized, token-efficient overview that defers detail to reference files, with a clear sequenced workflow. Its main gaps are the absence of any concrete code/config in the body and a broken plus an orphaned reference path.

Suggestions

Fix the broken 'troubleshooting/common-issues.md' reference (no such file exists) or remove the link, and add the unlinked references/environment-variables.md to the References list.

Include one small concrete snippet in the body (e.g. the WebSocket endpoint/auth header or a minimal connect example) so the skill is executable without immediately opening a reference.

Add an explicit validation checkpoint in the workflow (e.g. verify the connection is authenticated and receiving events before subscribing to the full event stream).

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line decision gate, six terse workflow steps, and a short reference list, with no concept explanations or padding, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Steps enumerate concrete subtasks (heartbeat, reconnect, backoff, token/auth, proxies, TLS interception) but provide no executable code, commands, or config snippets in the body, fitting 'Some concrete guidance but incomplete; missing key details'.	3 / 5
Workflow Clarity	A clear six-step sequence with an explicit justification gate (step 1), observability (step 5), and debug/recovery (step 6); validation is implicit rather than an explicit validate-then-proceed loop, so it sits at 4 not 5.	4 / 5
Progressive Disclosure	Structure is a concise overview plus well-signaled one-level-deep references, but the 'troubleshooting/common-issues.md' link points to a non-existent path and references/environment-variables.md is unlinked, which are organization gaps keeping it below 5.	4 / 5
	Total	16 / 20 Passed

Description

40%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 has an explicit 'Use when' trigger and a distinct niche, but it conflates what and when into a single vague clause and lacks concrete capability detail. It reads more as a trigger than a full description.

Suggestions

Split the description into a concrete 'what' clause and a 'when' clause, e.g. 'Establish persistent Zoom WebSocket connections with auth, heartbeat, reconnect, and event normalization. Use when you need real-time Zoom event delivery instead of HTTP webhooks.'

Add natural trigger synonyms and variations users might say, such as 'Zoom events', 'real-time Zoom delivery', or 'Zoom websockets vs webhooks'.

Name 1-2 concrete capabilities (e.g. 'connection lifecycle and event normalization') to lift specificity above a single generic verb.

Dimension	Reasoning	Score
Specificity	The phrase 'building Zoom WebSockets' names the domain but offers only a single generic action ('building') with no concrete sub-capabilities, matching the score-2 anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Only a 'when' trigger is present ('Use when building Zoom WebSockets') with no distinct statement of what the skill does, matching score-2 'only when is present without what'; it does not reach 3 because there is no clear 'what'.	2 / 5
Trigger Term Quality	'Zoom WebSockets' is a relevant, natural-sounding domain keyword, but no synonyms or variations (e.g. 'Zoom events', 'real-time', 'websockets vs webhooks') are given, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Zoom WebSockets' is a clear niche, but the description does not disambiguate from the sibling setup-zoom-webhooks skill (only the body does), leaving minor overlap risk per the score-4 anchor.	4 / 5
	Total	11 / 20 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: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/websockets/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.