Name: zoom
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zoom

Zoom integration. Manage Users. Use when the user wants to interact with Zoom data.

Quality

64%

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 ./skills/zoom/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 body is highly actionable with executable commands and a strong, validated connection workflow, but it is held back by an unnecessary Zoom-intro paragraph and the absence of any reference files for the large action/option tables that would benefit from progressive disclosure.

Suggestions

Remove or trim the introductory paragraph explaining what Zoom is; Claude already knows this.

Move the full popular-actions table and proxy-options table into a references/ file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Add a brief validation/caution note for destructive actions (e.g. delete-meeting) before showing the generic action-run command.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands and tables, but the opening paragraph explains what Zoom is ('a video conferencing platform... popular with businesses, educators') and includes light padding ('focus on the integration logic rather than auth plumbing') that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request proxy) with flag tables and a concrete actions table, fully covering the common cases.	5 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and explicit re-poll feedback loops; minor gap is the lack of validation/caution around destructive actions like delete-meeting listed in the table.	4 / 5
Progressive Disclosure	Well-sectioned with clear headings, but no bundle/reference files exist and all content—including an 11-row actions table and a proxy-options table that could be separate references—is inlined in a ~155-line SKILL.md, so content that should be split is inline.	3 / 5
	Total	15 / 20 Passed

Description

57%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 correctly signals a Zoom-specific niche with an explicit 'Use when' clause, but it is thin: it lists only one generic action and omits the richer trigger terms (meetings, webinars, recordings) that the body actually covers.

Suggestions

Expand the action list to concrete capabilities, e.g. 'Manage users, meetings, webinars, and recordings in Zoom.'

Broaden trigger terms to include natural phrases users say: 'Use when the user wants to manage Zoom users, schedule meetings, list recordings, or interact with Zoom data.'

Keep third-person voice (already compliant) while making the 'when' clause name specific Zoom objects rather than generic 'Zoom data'.

Dimension	Reasoning	Score
Specificity	Names the Zoom domain and a single generic action ('Manage Users'), but offers no concrete capabilities; matches the 'names domain but actions minimal/generic' anchor rather than the concrete-action anchor at 3.	2 / 5
Completeness	States both what ('Zoom integration. Manage Users.') and an explicit when ('Use when the user wants to interact with Zoom data.'), but the trigger clause is generic rather than concrete.	4 / 5
Trigger Term Quality	Relevant keywords ('Zoom', 'Users', 'interact with Zoom data') are present but common variations the body itself covers (meetings, webinars, recordings) are missing from the trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	'Zoom integration' is a clear niche with minimal conflict risk, though the thin trigger phrasing keeps it just below the distinct-triggers anchor at 5.	4 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zoom/SKILL.md
Commit: f484c82

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