CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-video-sdk-ios

Zoom Video SDK for iOS native apps. Use when building custom iOS video sessions with full UI control, token-based session auth, and event-driven media/participant flows.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/video-sdk/ios/SKILL.md
SKILL.md
Quality
Evals
Security

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 exemplary lean, well-signaled index — exactly the overview-pointer shape progressive disclosure wants — but it over-delegates: the body carries no task-level guidance of its own, and the primary reading path it advertises is largely absent from the bundle as provided, so the skill's substance is unreachable.

Suggestions

Add a minimal inline quick-start (e.g., the session-join sequence with the key ZoomVideoSDK calls or a token-fetch snippet) so the body provides some executable guidance instead of being purely navigational.

Restore or ship the referenced bundle files (ios.md, concepts/*, examples/session-join-pattern.md, scenarios/*, troubleshooting/common-issues.md, RUNBOOK.md) — six of nine 'Start Here' links and the RUNBOOK pointer currently resolve to nothing in the bundle.

If the skill involves risky or batch operations (session auth, participant management), include at least one validation checkpoint (e.g., verify token claims before joining) in the reading order to lift workflow clarity.

DimensionReasoningScore

Conciseness

The ~30-line body is pure navigation — an ordered "Start Here" file list, key external links, and a one-line RUNBOOK pointer — with no padding and no explanations of concepts Claude already knows. It matches anchor 5 ('lean and efficient; every token earns its place').

5 / 5

Actionability

The body itself contains no code, commands, or task-level steps — it is an ordered index of file paths plus external URLs. This rises above anchor 2 because the specific, ordered paths and the labeled RUNBOOK pointer are concrete directions, but it falls short of anchor 4 since no executable guidance for any actual task (e.g., joining a session, wiring a delegate) appears in the body.

3 / 5

Workflow Clarity

The numbered "Start Here" list gives a clear reading sequence but is not a task workflow: there are no validation checkpoints and the sequence collapses in practice because most linked files are absent from the bundle. This matches anchor 3 ('sequence present but checkpoints missing or implicit'), not anchor 4 which requires most checkpoints to be present.

3 / 5

Progressive Disclosure

Structure and signaling are good (one-level-deep, clearly labeled links — an anchor 4/5 shape), but scoring against the actual bundle structure: only references/ios-reference-map.md, references/environment-variables.md, and references/versioning-and-compatibility.md exist. Six of the nine "Start Here" targets (ios.md, concepts/lifecycle-workflow.md, concepts/architecture.md, examples/session-join-pattern.md, scenarios/high-level-scenarios.md, troubleshooting/common-issues.md) plus RUNBOOK.md are missing from the bundle, making navigation unreliable and dropping this to anchor 3.

3 / 5

Total

14

/

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.

A strong description: it names a specific niche, states concrete capabilities, and pairs them with an explicit 'Use when' trigger clause. The only weakness is that capabilities read slightly as a feature list rather than an exhaustive enumeration of actions, leaving minor coverage gaps.

DimensionReasoningScore

Specificity

Names the domain ("Zoom Video SDK for iOS native apps") and several concrete capabilities ("full UI control, token-based session auth, and event-driven media/participant flows"), matching the 'several specific actions; minor gaps' anchor. It falls short of anchor 5 because capabilities are feature phrases rather than a comprehensive list of actions (e.g., no explicit join/session/chat/share verbs), and is clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers what ("Zoom Video SDK for iOS native apps... full UI control, token-based session auth, and event-driven media/participant flows") and when ("Use when building custom iOS video sessions with...") with concrete trigger phrases, matching anchor 5 exactly. Anchor 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "Zoom Video SDK", "iOS", "video sessions", "token", "auth" — giving good keyword coverage per anchor 4. Not anchor 5 because a few natural synonyms users might say (e.g., "custom video app", "video call integration") are missing; clearly above anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"Zoom Video SDK for iOS native apps" carves out a clear niche with distinct triggers (custom video sessions, token-based session auth) and minimal conflict risk against meeting-SDK, non-iOS, or generic video skills. It matches anchor 5; anchor 4's 'minor overlap risk with closely related skills' does not apply given the platform- and product-specific framing.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/zoom/skills/video-sdk/ios/SKILL.md

Reviewed

Table of Contents

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.