CtrlK
BlogDocsLog inGet started
Tessl Logo

choose-zoom-approach

Use when choosing architecture.

47

Quality

50%

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/choose-zoom-approach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a well-crafted routing skill: a dense, specific decision table, clear guardrails, and an explicit deliverables checklist, all delivered concisely with appropriately signaled one-level references to sibling skills. It assumes Claude's competence and stays tightly scoped to its purpose.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and efficient, explains no concepts Claude already knows (no definition of Zoom, REST, or SDKs), and every line — the decision table, guardrails, and deliverables — earns its place.

3 / 3

Actionability

The decision-framework table maps concrete problem types to specific named surfaces with links, and the guardrails and "What To Produce" list give decisive, specific guidance; for an instruction-only routing skill this concrete guidance satisfies the score-3 bar without needing executable code.

3 / 3

Workflow Clarity

This is a single-decision routing skill whose action — match the problem type to a surface, apply guardrails, then produce the listed outputs — is unambiguous and well-sequenced, and it involves no destructive or batch operations that would require validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist, and the short body is well-organized into clear sections with sibling-skill references (e.g., ../rest-api/SKILL.md) signaled one level deep via markdown links, meeting the score-3 bar for compact skills.

3 / 3

Total

12

/

12

Passed

Description

0%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a minimal four-word trigger that states when to use the skill but never says what it does, and lacks any Zoom-specific vocabulary. It is overly generic and at high risk of conflicting with unrelated architecture skills.

Suggestions

Add a "what" clause naming the concrete action, e.g., "Routes a request to the smallest correct Zoom API surface (REST API, Webhooks, Meeting SDK, Video SDK, RTMS, Phone, etc.)."

Include Zoom-specific trigger terms users would actually say, e.g., "Use when choosing between Zoom APIs/SDKs, deciding REST vs Video SDK, or picking a Zoom integration approach."

Replace the generic word "architecture" with the Zoom domain to reduce overlap with unrelated architecture-decision skills.

DimensionReasoningScore

Specificity

The description names no concrete actions at all — "Use when choosing architecture" is an abstract trigger with no capability verbs, matching the score-1 anchor of vague/abstract language.

1 / 3

Completeness

It provides a "when" trigger but entirely omits the "what" — there is no statement of what the skill does, satisfying the score-1 anchor of missing what or when.

1 / 3

Trigger Term Quality

"choosing architecture" is overly generic jargon; a user needing Zoom-surface selection would say "which Zoom API/SDK", and the description includes no Zoom-specific keywords, so it falls below the score-2 example that at least names a domain.

1 / 3

Distinctiveness Conflict Risk

"choosing architecture" is very generic and would conflict with any architecture-decision skill; the absence of Zoom-specific terms makes it unlikely to be distinguishable, matching the score-1 anchor.

1 / 3

Total

4

/

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: 11 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.