CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-virtual-agent-ios

Zoom Virtual Agent iOS integration via WKWebView. Use for Swift/Objective-C script injection, message handlers, support_handoff relay, and URL routing policies.

61

Quality

77%

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/virtual-agent/ios/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

An exemplary token-efficient overview that names the right APIs and ordering guardrails, but it functions as a hub whose spokes are largely absent: three of four referenced files are missing, and without any executable snippet or validation step, the body alone cannot drive the integration. Conciseness is a model 5; the substance behind the links is the gap.

Suggestions

Include the referenced files (concepts/webview-lifecycle.md, examples/js-bridge-patterns.md, troubleshooting/common-issues.md) or remove/replace those links so every Quick Link resolves to real bundle content.

Add one short executable Swift snippet showing WKUserScript injection and message-handler registration so the core flow is copy-paste ready without external files.

Add a validation checkpoint to the Integration Model (e.g., confirm scripts and handlers are registered before the campaign URL loads) to elevate workflow clarity.

DimensionReasoningScore

Conciseness

Roughly 30 lean lines with no padding and no explanation of concepts Claude already knows (no 'what is WKWebView' prose). Every bullet carries non-obvious, specific guidance ('Inject window.zoomCampaignSdkConfig using WKUserScript'), matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

Names concrete APIs and identifiers (WKUserScript, window.zoomCampaignSdkConfig, SFSafariViewController) but provides no executable code or commands, and defers key details to links where 3 of the 4 referenced files do not exist in the bundle. This fits anchor 3 (concrete but incomplete, key details missing), below the executable anchor 4 and above the high-level-hints anchor 2.

3 / 5

Workflow Clarity

The Integration Model gives a real sequence (load campaign URL, inject script, register handlers, handle URL behavior) and one guardrail fixes ordering ('Register scripts and handlers before web interaction'), but there are no validation checkpoints (e.g., verify handler registration or script injection succeeded). Anchor 3: sequence present, checkpoints missing.

3 / 5

Progressive Disclosure

Scored against the actual bundle: of the four Quick Links, only references/ios-reference-map.md exists; concepts/webview-lifecycle.md, examples/js-bridge-patterns.md, and troubleshooting/common-issues.md are absent, so navigation is broken for most links despite one-level-deep structure. This falls to anchor 2 rather than 3, because the problem is missing referenced content, not organization.

2 / 5

Total

13

/

20

Passed

Description

83%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: concrete, third-person, with an explicit 'Use for' trigger clause listing specific capabilities and real API names. Minor gains available in keyword synonyms and separating niche boundaries from sibling Zoom iOS skills.

Suggestions

Add natural synonyms users might say, such as 'chatbot' or 'virtual agent handoff', alongside the technical terms to broaden trigger coverage.

State the platform/SDK boundary explicitly (e.g., 'use for Zoom Virtual Agent, not Zoom Contact Center iOS integrations') to reduce overlap risk with sibling Zoom mobile skills.

DimensionReasoningScore

Specificity

Names the domain ('Zoom Virtual Agent iOS integration via WKWebView') and several concrete actions ('script injection, message handlers, support_handoff relay, and URL routing policies'), matching the 'several specific actions with minor gaps' anchor. Not 5 because coverage omits capabilities surfaced in the body (iOS 14.5+ download behavior, deprecated openURL fallback).

4 / 5

Completeness

Explicitly answers both: what ('Zoom Virtual Agent iOS integration via WKWebView') and when ('Use for Swift/Objective-C script injection, message handlers, support_handoff relay, and URL routing policies') with concrete trigger phrases, mirroring the anchor-5 example structure. The 'Use for' clause is equivalent explicit trigger guidance, so it is not capped at 3.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'Zoom Virtual Agent', 'iOS', 'Swift/Objective-C', 'message handlers'. A few natural variants are missing (e.g., 'chatbot', 'handoff', 'iOS SDK'), so it fits anchor 4 rather than the comprehensive-synonym coverage of anchor 5, and is well above the partial coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

Clear product-and-platform niche with distinct triggers, but closely related sibling Zoom mobile skills (e.g., a Contact Center iOS skill) create minor overlap risk, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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: 3 missing, 2 suspicious

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/zoom/skills/virtual-agent/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.