zoom-video-sdk-android

Zoom Video SDK for Android native apps. Use when building custom Android video experiences with full UI control, session tokens, raw media options, and event-driven participant state.

Quality

62%

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/video-sdk/android/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is admirably lean and well-structured as a navigation hub, but it provides no executable guidance and most of its file links point to files that are not actually present in the bundle. Adding at least a minimal concrete example and supplying the referenced files would substantially raise quality.

Suggestions

Include at least one minimal executable snippet (e.g. the join-session call sequence with session token) so the skill is actionable without chasing every link.

Create the referenced bundle files (android.md, concepts/*, examples/*, scenarios/*, troubleshooting/common-issues.md, RUNBOOK.md) or remove links to files that do not exist so navigation is not broken.

Add a brief validation/checklist step for the join lifecycle (token fetch -> join -> verify session state) so the workflow has an explicit checkpoint rather than only a reading order.

Dimension	Reasoning	Score
Conciseness	The body is a lean navigation index ("Start Here" list, "Key Sources", "Operations") with no padded explanations of what video or SDKs are; every line is a pointer and assumes Claude's competence, matching the lean-and-efficient anchor.	3 / 3
Actionability	There is no concrete, executable guidance anywhere in the body — no code, commands, API calls, or examples; it only describes where to read more ("Start Here\n1. [android.md](android.md)") rather than instructing, matching the describes-rather-than-instructs anchor.	1 / 3
Workflow Clarity	The numbered "Start Here" list provides a reading-order sequence, but there are no validation checkpoints or feedback loops and it is navigation rather than an operational workflow, matching the steps-listed-but-checkpoints-missing anchor.	2 / 3
Progressive Disclosure	The structure is a clean one-level-deep table of contents, but against the actual bundle most referenced files are missing — only references/.md exist while android.md, concepts/, examples/, scenarios/, troubleshooting/*, RUNBOOK.md, and ../SKILL.md do not, so navigation points largely to non-existent content.	2 / 3
	Total	8 / 12 Passed

Description

75%

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 has an explicit use-trigger and a clear, distinct niche, but leads with SDK feature jargon rather than natural user keywords and concrete verbs. Rewording around actions and everyday video terms would lift specificity and trigger quality.

Suggestions

Lead with concrete actions users want, e.g. "Join and manage real-time video sessions, subscribe to audio/video streams, and render custom Android video UIs."

Add natural trigger variations a user would actually say ("video call", "video conference", "real-time video", "Zoom Video SDK") alongside the SDK terms.

Keep the explicit "Use when..." clause but tie the conditions to user-facing scenarios (custom in-app video, raw media access) rather than only SDK feature names.

Dimension	Reasoning	Score
Specificity	Names the Android video SDK domain and lists specific features ("full UI control, session tokens, raw media options, and event-driven participant state"), but these are capability areas rather than multiple concrete actions (e.g. join/subscribe/render), so it sits at the names-domain-but-not-comprehensive anchor.	2 / 3
Completeness	It answers both what ("Zoom Video SDK for Android native apps") and when via an explicit "Use when building custom Android video experiences..." clause, which clears the missing-trigger cap and matches the both-what-and-when anchor.	3 / 3
Trigger Term Quality	"Android video experiences" are terms a user might say, but "session tokens", "raw media options", and "event-driven participant state" are SDK jargon, and common natural variations like "video call", "video conference", or "real-time video" are absent, matching some-relevant-keywords-but-missing-variations.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply bounded (Android native + Zoom Video SDK + custom UI control), giving distinct triggers unlikely to overlap with generic video or cross-platform skills.	3 / 3
	Total	10 / 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: 7 missing, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/video-sdk/android/SKILL.md
Commit: 11c74d6

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