zoom-meeting-sdk-android

Zoom Meeting SDK for Android native apps. Use when embedding Zoom meetings in Android with default/custom UI, PKCE + SDK auth, join/start flows, and Meeting SDK API integration.

Quality

79%

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/meeting-sdk/android/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 an admirably lean, well-structured router with clear sequencing and decision rules. Its main weaknesses are that actionable implementation detail lives entirely in linked files (none inline) and that the majority of referenced bundle paths are absent from the provided skill bundle, weakening progressive disclosure.

Suggestions

Inline a minimal executable snippet (e.g., the Gradle dependency line and the SDK init call) so the SKILL.md is actionable without immediately opening another file.

Verify the Start Here links resolve to real files in the bundle; either ship the missing concepts/examples/scenarios/troubleshooting files or trim the list to existing references.

Add one explicit validation/feedback checkpoint for the join→start flow (e.g., 'confirm onMeetingStatus JOINED before enabling custom UI') to lift workflow clarity above a routing-level sequence.

Dimension	Reasoning	Score
Conciseness	Lean routing/index doc that assumes Claude's competence — no padding, no explanation of what Zoom or Android is, every line earns its place.	5 / 5
Actionability	Routing notes give concrete decision rules ("Use default UI first", "Move to custom UI once auth... stable", "chain with..."), but the actual executable implementation steps are deferred to linked files with no inline code or commands.	3 / 5
Workflow Clarity	A clear progression is present — Start Here 1-9 reading order plus a default-UI→custom-UI dev sequence with a validation gate ("first successful join/start validation") — with only minor checkpoint gaps.	4 / 5
Progressive Disclosure	Structure and signaling are clean (numbered one-level-deep references, grouped concepts/examples/scenarios/references/troubleshooting), but most Start Here paths (android.md, concepts/, examples/, scenarios/, troubleshooting/, RUNBOOK.md, signature-playbook.md) do not exist in the provided bundle, so navigation is partially broken.	3 / 5
	Total	15 / 20 Passed

Description

87%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 lean, third-person, and clearly pairs a what-statement with an explicit Use-when trigger listing concrete capability areas. It is highly distinctive and low-conflict; the only minor weakness is that the action list reads as capability facets rather than fully concrete actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — "default/custom UI", "PKCE + SDK auth", "join/start flows", "Meeting SDK API integration" — but stays at the level of capability facets rather than enumerating concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("Zoom Meeting SDK for Android native apps") and when ("Use when embedding Zoom meetings in Android with...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ("Zoom meetings", "Android", "embedding Zoom meetings", "Meeting SDK"), with good coverage but missing common synonyms like "video conferencing" or "Zoom calls".	4 / 5
Distinctiveness Conflict Risk	The Android-specific + Zoom-Meeting-SDK combination carves a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	18 / 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: 7 missing, 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/meeting-sdk/android/SKILL.md
Commit: 1dc1958

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