CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-contact-center-ios

Zoom Contact Center SDK for iOS. Use for native iOS chat/video/ZVA/scheduled callback integrations, app lifecycle bridging, rejoin flow, and callback handling.

56

Quality

71%

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

Quality

Content

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

A very lean, well-sectioned hub that names the right SDK symbols and guardrails without a wasted token. Its weaknesses are that it defers all workflow and code detail to bundle files that are missing, and its quick links are mostly broken, leaving the reader with pointers that resolve to nothing.

Suggestions

Fix the bundle navigation: either add the missing files (concepts/sdk-lifecycle.md, examples/service-patterns.md, troubleshooting/common-issues.md, RUNBOOK.md) or remove/repair the links — currently 6 of 7 referenced paths resolve to nothing.

Add a minimal inline initialization sequence (set ZoomCCContext -> item-based initializeWithItem -> channel operation) with a short Swift snippet so the skill is actionable without the missing reference files.

Correct the lifecycle method typo ("appDidEnterBackgroud" -> "appDidEnterBackground") and align lifecycle forwarding steps with the video/rejoin path so the implied workflow is at least coherently ordered.

DimensionReasoningScore

Conciseness

The body is entirely lean pointer lists ("Manager: ZoomCCInterface.sharedInstance()", "Official docs" URLs, guardrail bullets) with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

Concrete symbols are named ("ZoomCCContext", "appDidBecomeActive", "scheduledCallbackService") and guardrails are directive, but there is no executable code or command, and the details are deferred to files that do not exist in the bundle. This fits 3 (some concrete guidance, incomplete, missing key details) better than 4 (mostly executable guidance) or 2 (minimal concrete guidance).

3 / 5

Workflow Clarity

No step sequence is written out; only an ordering constraint ("Set ZoomCCContext before channel operations") and a list of lifecycle methods to forward imply a partial flow. That is a rough, poorly defined sequence with no validation — the 2 anchor — rather than 3's listed-but-unvalidated steps.

2 / 5

Progressive Disclosure

Section headers are clean and references are one level deep and clearly signaled, but scored against the actual bundle, 6 of the 7 referenced paths (concepts/sdk-lifecycle.md, examples/service-patterns.md, troubleshooting/common-issues.md, RUNBOOK.md, and both ../../ cross-skill chains) do not exist — only references/ios-reference-map.md resolves. The navigation promise fails for most links, which is minimal effective structure.

2 / 5

Total

12

/

20

Passed

Description

75%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 solid, concise description with an explicit use-when clause, good natural trigger terms, and a clearly scoped niche. It scores consistently at the 4 anchor across dimensions: specific but not comprehensive, well-targeted but with minor overlap risk against sibling Zoom skills.

DimensionReasoningScore

Specificity

"native iOS chat/video/ZVA/scheduled callback integrations, app lifecycle bridging, rejoin flow, and callback handling" lists several concrete capability areas with minor gaps (core SDK operations like initialize/login/logout are not named). It exceeds the 3 anchor (only 1-2 concrete actions) but falls short of 5's comprehensive action coverage.

4 / 5

Completeness

Both parts are present: the "what" ("Zoom Contact Center SDK for iOS") and an explicit "Use for..." trigger clause. Not 5 because the "what" is a subject statement rather than a concrete statement of what the skill does, and the "when" could be more specific; not 3 because the when-clause is explicit rather than missing or weakly implied.

4 / 5

Trigger Term Quality

Natural terms users would say include "chat", "video", "ZVA", "scheduled callback", "rejoin", "callback", and "iOS", giving good keyword coverage. A few natural variations are missing (e.g., "ZoomCC", "Contact Center chat", "voice assistant"), so it does not reach the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Zoom Contact Center SDK for iOS" carves a clear niche with distinct triggers (ZVA, rejoin flow, scheduled callback). Minor overlap risk remains with sibling skills (Zoom Apps SDK and OAuth are cross-linked as related chains), keeping it below 5.

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

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/zoom/skills/contact-center/ios/SKILL.md

Revision

0722921

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill