zoom-apps-sdk

Use when using Apps SDK.

Quality

46%

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/zoom-apps-sdk/SKILL.md

Quality

Content

65%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 an efficiently written, well-sequenced overview that assumes competence and points outward, but it stays at a procedural level with no executable code or validation checkpoints, and its reference section is largely broken. Fixing the references and adding concrete SDK call examples would lift it substantially.

Suggestions

Add a minimal executable snippet for the core action, e.g. a zoomSdk initialization and capability-gating example, so step 3 is copy-paste ready.

Insert explicit validation checkpoints into the workflow (e.g. 'Verify the app loads and required capabilities are granted before advancing to step 5').

Repair the References section: remove or create the missing concepts/, examples/, and troubleshooting/ paths, and add links to the existing but currently orphaned references/apis.md, oauth.md, events.md, environment-variables.md, and zmail-sdk.md.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean and assumes Claude's competence: no padding, no explanation of what a Zoom App or OAuth is, and every line is structural or actionable, matching 'lean and efficient; every token earns its place.'	5 / 5
Actionability	The workflow names concrete concepts (zoomSdk, allowed domains, redirect URIs, Layers API, CSP) but provides no executable code, commands, or API-call examples, so guidance is specific yet incomplete.	3 / 5
Workflow Clarity	A clear, logical 6-step sequence exists with one soft gate ('only after the base app loads reliably'), but explicit validation checkpoints and error-recovery feedback loops are missing.	3 / 5
Progressive Disclosure	The overview form is clean with one-level-deep, labeled references, but 5 of 7 referenced paths do not exist in the bundle and 5 real bundle files (apis.md, oauth.md, events.md, environment-variables.md, zmail-sdk.md) are not linked, making navigation unreliable.	3 / 5
	Total	14 / 20 Passed

Description

28%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 is minimal trigger-only guidance: it tells Claude when to fire but not what the skill does, using a single technical keyword rather than natural user phrasing. It needs a concrete capability statement and natural synonyms to rise above a weak score.

Suggestions

Add a concrete 'what' clause naming the actions the skill performs, e.g. 'Initialize and call the Zoom Apps SDK, configure in-client OAuth, and manage running contexts.'

Broaden trigger terms with natural user phrasing and synonyms such as 'Zoom App', 'Zoom Apps SDK', and 'in-client app' rather than only 'Apps SDK'.

Add a brief disambiguation cue in the description (e.g. 'for apps running inside the Zoom client, not embedding meetings externally') to reduce conflict with a Meeting SDK skill.

Dimension	Reasoning	Score
Specificity	The description 'Use when using Apps SDK.' names the domain ('Apps SDK') but states no concrete actions or capabilities at all, placing it at the 'names the domain but actions are minimal or generic' anchor rather than the entirely-vague 1.	2 / 5
Completeness	Only the 'when' is present ('Use when using Apps SDK') with no 'what does this do' clause, matching the anchor 'only when is present without what'; the explicit trigger keeps it from a 1.	2 / 5
Trigger Term Quality	It offers a single technical keyword ('Apps SDK') and omits the natural phrases a user would actually say ('Zoom App', 'build a Zoom App', 'in-client app'), fitting 'one or two keywords; missing the natural phrases users say.'	2 / 5
Distinctiveness Conflict Risk	'Apps SDK' denotes a specific niche, but the description does not disambiguate it from the closely related Meeting SDK skill, leaving real overlap risk for a user who says 'Zoom SDK'.	3 / 5
	Total	9 / 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: 5 missing	Warning

	Total	15 / 16 Passed

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