ui-toolkit

Use when using Zoom UI Toolkit.

Quality

54%

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/ui-toolkit/SKILL.md

Quality

Content

68%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 a tight, well-structured overview that routes to detailed references rather than inlining them, but it lacks executable guidance and validation checkpoints, and one of its reference links is broken.

Suggestions

Fix or remove the missing references/troubleshooting/common-issues.md link (the troubleshooting/ directory does not exist) so all references resolve.

Add at least one concrete executable snippet (e.g. the UI Toolkit mount/init code or a sample signature-generation call) so the most common case is copy-paste ready.

Insert a validation checkpoint in the workflow (e.g. verify the session joins and media permissions are granted before configuring chat/captions) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a one-line purpose, a six-step workflow, and a reference list with no padding or explanation of concepts Claude already knows, matching the "every token earns its place" anchor.	5 / 5
Actionability	The workflow names concrete configuration areas (join, leave, media permissions, chat, captions, recordings, theming) but provides no executable code, commands, or specifics — key details are deferred to references, matching the "some concrete guidance but incomplete" anchor.	3 / 5
Workflow Clarity	A clear numbered sequence with built-in routing decisions is present, but there are no validation or verification checkpoints, matching the "steps listed but checkpoints missing" anchor; it avoids a lower score because the sequence is coherent and well-ordered.	3 / 5
Progressive Disclosure	The body is an overview with well-signaled, one-level-deep references to full-guide.md and environment-variables.md, but the referenced troubleshooting/common-issues.md does not exist in the bundle, a navigation gap that keeps it below a 5.	4 / 5
	Total	15 / 20 Passed

Description

40%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 a bare trigger clause that names the product but says nothing about what the skill actually does, leaving both specificity and completeness weak. It is distinct enough to avoid most conflicts but too sparse to be a strong activation signal.

Suggestions

Add a "what" clause stating concrete capabilities, e.g. "Mount Zoom Video SDK UI Toolkit for prebuilt web session UIs — join, chat, captions, recordings, and theming."

Expand trigger terms with natural synonyms users might say ("Zoom Video SDK web UI", "prebuilt Zoom session", "Zoom UI Toolkit widget").

Use third-person action verbs to describe what the skill does rather than only when to invoke it.

Dimension	Reasoning	Score
Specificity	The description "Use when using Zoom UI Toolkit" names the specific product domain but states zero concrete actions or capabilities, matching the anchor that names a domain with minimal/generic actions rather than the entirely-vague anchor.	2 / 5
Completeness	Only the "when" is present ("Use when using Zoom UI Toolkit") with no statement of what the skill does, matching the anchor where only "when" appears without "what"; it is not below 2 because it is not entirely vague.	2 / 5
Trigger Term Quality	It includes a natural trigger ("Use when using") plus the product keyword "Zoom UI Toolkit", but offers only that single phrase with no synonyms or variations, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific "Zoom UI Toolkit" product gives it a clear distinct niche with only minor overlap risk against sibling Zoom SDK skills; it is not a 5 because the phrasing is generic and the body reveals routing overlap with related Video/Meeting SDK skills.	4 / 5
	Total	11 / 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: 1 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

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