build-zoom-bot

Use when building bots.

Quality

52%

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/build-zoom-bot/SKILL.md

Quality

Content

72%

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-structured, token-efficient router skill that appropriately delegates detail to one-level-deep sub-skills. Its main gaps are actionability and workflow clarity: several workflow steps are vague directives, and there are no validation checkpoints.

Suggestions

Tighten vague steps: replace 'Call out environment and lifecycle constraints early' with the specific constraints to surface (e.g. OAuth/scopes, app approval, bot lifecycle events, rate limits) and where to document them.

Add a lightweight validation or decision checkpoint to the workflow (e.g. confirm join authority and auth model before routing to the SDK, and verify webhook subscription scope before relying on async events).

Dimension	Reasoning	Score
Conciseness	The body is lean — bullet-pointed scope, a four-step workflow, and concise reference links — with no padding or explanations of concepts Claude already knows, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	It names concrete components (Meeting SDK, RTMS, REST API, Webhooks) and routes to specific sub-skills, but steps like 'Call out environment and lifecycle constraints early' are vague directives with no executable detail or specifics, matching 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The four steps are clearly sequenced (clarify → route to SDK/RTMS → add APIs → flag constraints), but there are no validation checkpoints or feedback loops, matching 'sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	It is a clean overview that routes to five clearly-signaled, one-level-deep sub-skills (meeting-sdk, rtms, scribe, rest-api, webhooks) under a 'Primary References' section, with content appropriately split across the skill library, matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	10 / 12 Passed

Description

32%

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 too generic: it provides an explicit trigger but names no concrete capabilities and does not distinguish Zoom/meeting bots from the broad universe of bot skills. It would likely fire for the wrong skill.

Suggestions

Replace 'Use when building bots.' with a description that lists concrete actions, e.g. 'Build Zoom meeting bots that join sessions, capture real-time media and transcripts, and orchestrate post-meeting processing. Use when the user wants to build a Zoom or meeting bot that joins, observes, transcribes, or summarizes live sessions.'

Add Zoom/meeting-specific trigger terms ('Zoom bot', 'meeting bot', 'RTMS', 'join meetings', 'live transcription') so the skill is distinguishable from Discord/Slack/chatbot skills.

Ensure the description answers both 'what' (joins meetings, captures media, handles RTMS) and 'when' (building Zoom/meeting bots) explicitly.

Dimension	Reasoning	Score
Specificity	The phrase 'building bots' names a domain but describes zero concrete actions (no joining, transcribing, capturing, or summarizing), matching the 'vague or no actions; abstract language' anchor.	1 / 3
Completeness	It has an explicit 'when' trigger ('Use when building bots') and a loose 'what', but the capability is never concretely described, so it falls short of 'clearly answers both what AND when' (3) while not missing 'when' entirely (1).	2 / 3
Trigger Term Quality	'bots' is a natural term a user might say, but it is generic and omits common variations ('Zoom', 'meeting', 'transcription', 'RTMS') that would sharpen the trigger, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	'bots' carries no Zoom or meeting qualifier, so it would conflict with many other bot-building skills (Discord, Slack, Telegram, chatbots), matching 'very generic; would conflict with many skills'.	1 / 3
	Total	6 / 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 suspicious	Warning

	Total	15 / 16 Passed

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