CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-meeting-sdk-unreal

Zoom Meeting SDK for Unreal Engine wrapper integrations. Use when building Unreal projects that embed Zoom meetings with C++ and Blueprint wrappers, including wrapper-to-SDK mapping concerns.

55

Quality

69%

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/unreal/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 maximally lean and well-structured as a one-level-deep index, but it is only an index: it contains no executable guidance, and most of the files it points to (8 of 11 paths) are absent from the bundle, so the progressive-disclosure structure fails in practice.

Suggestions

Add the missing bundle files (unreal.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 links that reference them.

Include a minimal quick-start snippet or concrete step sequence in SKILL.md itself (e.g., the join/start call flow with the key wrapper functions) so the skill is actionable without resolving every reference.

Annotate each 'Start Here' entry with a one-line description of what it contains and when to consult it, so navigation survives individual files being unavailable.

DimensionReasoningScore

Conciseness

A 33-line pure index: no padding, no explanations of concepts Claude already knows, and every line is either a link, a source URL, or a one-line pointer. Matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The body provides only high-level pointers (a numbered link list and two doc URLs) with no code, commands, or executable steps, and 8 of the 11 referenced paths (e.g., unreal.md, concepts/lifecycle-workflow.md, RUNBOOK.md) do not exist in the bundle. Not 1 because it does point to specific named files in a defined order; not 3 because nothing in the body itself constitutes concrete, executable guidance.

2 / 5

Workflow Clarity

The 'Start Here' numbered list is a reading order, not a task workflow — there is no sequenced process for performing an integration, no checkpoints, and no error-recovery guidance. Matches 'rough sequence present but many gaps; steps poorly defined'.

2 / 5

Progressive Disclosure

The design is a clean one-level-deep, clearly-signaled reference index, but scored against the actual bundle: only 3 of 11 referenced files (the three references/*.md) exist; unreal.md, both concepts/ files, examples/, scenarios/, troubleshooting/common-issues.md, and RUNBOOK.md are missing, breaking navigation. Not 4 because the majority of references being broken is more than a minor organization gap; not 2 because structure and signaling are good where files do exist.

3 / 5

Total

12

/

20

Passed

Description

73%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 concise, third-person description with an explicit 'Use when' trigger and excellent niche distinctiveness. Its main weakness is that the 'what' names the domain and one or two actions rather than enumerating several concrete capabilities.

Suggestions

Enumerate 2-3 concrete capability actions in the description (e.g., 'Set up SDK auth/join flows, map Blueprint and C++ wrapper calls to base SDK methods, and manage SDK lifecycle in Unreal projects').

Add common trigger variations users would naturally say, such as 'UE5', 'Unreal plugin', or 'Zoom plugin for Unreal'.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('embed Zoom meetings with C++ and Blueprint wrappers', 'wrapper-to-SDK mapping concerns') but does not list several specific capability actions, matching the 'names domain and 1-2 concrete actions' anchor. Not 4 because coverage is not comprehensive; not 2 because the actions given are domain-specific rather than generic.

3 / 5

Completeness

Both parts are present: 'what' ('Zoom Meeting SDK for Unreal Engine wrapper integrations') and an explicit 'Use when building Unreal projects that embed Zoom meetings...' clause. Not 5 because the 'what' states the domain rather than concrete capability actions; not 3 because the 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say ('Zoom', 'Meeting SDK', 'Unreal Engine', 'Blueprint', 'C++'), but a few common variations are missing ('UE5', 'Unreal plugin', '.uproject'). Not 5 because synonyms and file extensions are absent; not 3 because coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Zoom Meeting SDK + Unreal Engine + C++/Blueprint wrappers) with distinct triggers and minimal conflict risk against generic skills. Firmly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

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/meeting-sdk/unreal/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.