CtrlK
BlogDocsLog inGet started
Tessl Logo

zoom-meeting-sdk-macos

Zoom Meeting SDK for macOS native apps. Use when embedding Zoom meetings in macOS with default/custom UI, PKCE + SDK auth, host start/join flows, and desktop meeting feature controllers.

58

Quality

67%

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/meeting-sdk/macos/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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

The SKILL.md body is a tidy navigation overview with good intent and sectioning, but as bundled it is largely non-actionable: six of nine referenced files are missing and the body itself contains no executable guidance or code.

Suggestions

Ship the missing referenced files (macos.md, concepts/lifecycle-workflow.md, concepts/architecture.md, examples/join-start-pattern.md, scenarios/high-level-scenarios.md, troubleshooting/common-issues.md, RUNBOOK.md) or remove the broken links so the Start Here sequence is followable.

Add a minimal inline quick-start snippet (e.g., the SDK auth / PKCE token step or a host start/join call) so the skill is actionable without immediately requiring the missing detail files.

Add an explicit validation/checkpoint step in the workflow (e.g., verify the SDK initializes before proceeding to join) to strengthen workflow clarity for the multi-step start/join flow.

DimensionReasoningScore

Conciseness

The body is a lean overview that does not re-explain concepts Claude already knows; every line is navigation or a source pointer with no padding.

3 / 3

Actionability

The body provides no concrete code, commands, or examples — only links — and six of the nine referenced entry points (macos.md, concepts/*, examples/*, scenarios/*, troubleshooting/*, RUNBOOK.md) resolve to missing files, leaving no executable guidance in the skill as bundled.

1 / 3

Workflow Clarity

A numbered 'Start Here' sequence is present, but it has no validation checkpoints and the majority of its steps point to files that do not exist, so the intended workflow cannot actually be followed.

2 / 3

Progressive Disclosure

Structure is well signaled with distinct sections and one-level-deep references, but against the actual bundle only references/macos-reference-map.md, references/environment-variables.md, and references/versioning-and-compatibility.md exist; the other six referenced paths are broken, undermining navigation.

2 / 3

Total

8

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 concise, well-targeted description that names specific capabilities and includes an explicit 'Use when' trigger. Its only weakness is limited variation in natural trigger terms beyond 'Zoom meetings' and 'macOS'.

DimensionReasoningScore

Specificity

Names concrete capabilities beyond a generic domain: 'embedding Zoom meetings in macOS', 'default/custom UI', 'PKCE + SDK auth', 'host start/join flows', and 'desktop meeting feature controllers'.

3 / 3

Completeness

Explicitly answers what ('Zoom Meeting SDK for macOS native apps') and when ('Use when embedding Zoom meetings in macOS with...'), satisfying the 'Use when...' trigger requirement.

3 / 3

Trigger Term Quality

Includes natural terms like 'Zoom meetings' and 'macOS', but lacks common variations a user might say (e.g., 'video calls', 'Zoom on Mac', 'start a meeting') beyond the single SDK phrasing.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Zoom Meeting SDK', 'macOS', 'PKCE + SDK auth', and 'host start/join flows' carves a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing, 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.