CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-zoom-websockets

Use when building Zoom WebSockets.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/websockets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is an efficient, well-structured overview that appropriately delegates depth to bundle files, but it lacks executable specifics, explicit validation checkpoints, and one referenced file is missing. Tightening actionability and fixing the broken reference would raise the score.

Suggestions

Add at least one concrete, executable snippet (e.g. the WebSocket connect/auth/heartbeat sequence or a sample event handler) so the body is actionable without forcing a reference hop.

Insert an explicit validation checkpoint in the workflow, such as "Verify the connection authenticates and receives a heartbeat within N seconds; if not, re-check token and subscription settings before proceeding."

Fix or remove the broken reference to troubleshooting/common-issues.md, either by creating the file or pointing to an existing reference.

DimensionReasoningScore

Conciseness

The body is a lean overview that never explains what WebSockets are or pads with background; it assumes Claude's competence and defers detail to references, so every token earns its place.

3 / 3

Actionability

Steps like "Implement connection setup, authentication, heartbeat, reconnect, backoff, and shutdown handling" enumerate concrete subtasks but give no executable code, commands, or specifics — the "how" is entirely delegated to references.

2 / 3

Workflow Clarity

A clear six-step numbered sequence exists with a justify-or-reject first step, but for fragile connection work there are no explicit validation/verification checkpoints or feedback loops — observability and debug steps are present but implicit.

2 / 3

Progressive Disclosure

The structure is a concise overview with clearly labeled one-level references (full-guide, connection, events), but the referenced troubleshooting/common-issues.md path does not exist in the bundle, breaking navigation.

2 / 3

Total

9

/

12

Passed

Description

57%

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 concise and distinctive with a clear trigger, but it is too thin on the "what" — only the abstract action "building" is named, with no concrete capabilities enumerated. Adding specific actions would lift specificity and completeness.

Suggestions

List concrete capabilities after the trigger, e.g. "Use when building Zoom WebSockets to receive persistent real-time Zoom events: configure event subscriptions, manage connection/auth/heartbeat/reconnect, and normalize events."

Add natural trigger variations users might say, such as "Zoom real-time events", "Zoom event stream", or "persistent Zoom event delivery".

Keep the "Use when..." clause but pair it with an explicit one-line "what" so both dimensions are answered.

DimensionReasoningScore

Specificity

Quotes "building Zoom WebSockets" — it names the domain clearly but offers only the single vague action "building" rather than concrete capabilities like connection, heartbeat, or event handling.

2 / 3

Completeness

The explicit "Use when building..." trigger answers "when", but "what" is only implied; no concrete actions are listed, so it does not reach the explicit what-AND-when anchor.

2 / 3

Trigger Term Quality

"Zoom WebSockets" is a natural term a user would say, but coverage is thin and misses common variations such as real-time Zoom events, event streams, or persistent connections.

2 / 3

Distinctiveness Conflict Risk

"Zoom WebSockets" carves a clear niche and contrasts with the sibling webhooks skill, making it unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

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.