setup-zoom-webhooks

Use when building Zoom webhooks.

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 concise and well-structured with a clear sequenced workflow and labeled references, but it lacks executable examples, an explicit feedback loop, and has a broken reference plus orphaned bundle files. Strong on token efficiency, weaker on actionability and navigation integrity.

Suggestions

Fix the broken reference to troubleshooting/common-issues.md (the directory does not exist) and surface the orphaned references/environment-variables.md and references/verification.md files in the References list.

Add at least one executable example (e.g. a signature-verification snippet or a curl endpoint-validation command) so the most concrete steps go beyond high-level guidance.

Insert an explicit validate→fix→retry step (e.g. verify the signature; on mismatch reject and log; rely on idempotent handlers for retries) to strengthen the workflow checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows (no "what a webhook is" padding); each line is actionable guidance and the opening disambiguation against websockets earns its place, matching the "lean, every token earns its place" anchor.	3 / 3
Actionability	The workflow names concrete things to implement (endpoint/signature verification, idempotent handlers, a queue) but provides no executable code or commands and defers all "how" to references, matching "some concrete guidance but incomplete, missing key details" rather than the copy-paste-ready bar of a 3.	2 / 3
Workflow Clarity	There is a clear numbered sequence with ordering constraints ("before creating subscriptions", "before processing business logic") and a verification step, but no explicit validate→fix→retry feedback loop, so it sits at the "sequence present but checkpoints implicit" anchor rather than a 3.	2 / 3
Progressive Disclosure	The overview is concise with well-labeled one-level-deep references, but the referenced troubleshooting/common-issues.md does not exist in the bundle while references/environment-variables.md and references/verification.md are unreferenced, so navigation is not fully reliable — matching the "could be better organized" anchor rather than a clean 3.	2 / 3
	Total	9 / 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 terse, single-sentence trigger with an explicit "Use when" clause but almost no concrete capabilities or trigger variations, and no disambiguation from the websockets sibling. It is serviceable but under-specified for what the skill actually does.

Suggestions

Add concrete capabilities, e.g. "Create Zoom webhook subscriptions, verify endpoint and request signatures, and handle idempotent event delivery."

Include natural trigger variations users would say, e.g. "Use when integrating Zoom events, notifications, or webhook callbacks over HTTP."

Add disambiguation so it does not conflict with setup-zoom-websockets, e.g. "Use for HTTP event delivery; for persistent low-latency streams use setup-zoom-websockets."

Dimension	Reasoning	Score
Specificity	The phrase "building Zoom webhooks" names the domain but lists no concrete actions (no mention of subscriptions, signature verification, or idempotent delivery), matching the "vague/abstract, no concrete actions" anchor; it does not reach 2 because it names no specific actions at all.	1 / 3
Completeness	It has an explicit "Use when..." trigger (the "when") but the "what" is only weakly implied by the generic verb "building", so it does not clearly answer both what and when as required for a 3; it clears 1 because the trigger clause is explicit rather than missing.	2 / 3
Trigger Term Quality	"Zoom webhooks" is a relevant natural keyword a user might say, but only one term is present with no common variations (e.g. "Zoom events", "Zoom notifications", "Zoom integration"), matching the "some relevant keywords but missing common variations" anchor rather than the full coverage of a 3.	2 / 3
Distinctiveness Conflict Risk	"Zoom webhooks" is a fairly specific niche, but the description gives no disambiguation against the sibling setup-zoom-websockets skill (noted in the body), so it could still overlap with a similar skill rather than having clearly distinct triggers.	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: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/webhooks/SKILL.md
Commit: 11c74d6

Reviewed: 1 day 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.