CtrlK
BlogDocsLog inGet started
Tessl Logo

start

Use when starting Zoom work.

60

Quality

70%

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

Quality

Content

100%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 body is a well-structured, lean routing skill: an explicit routing table, a cleanly signaled supporting-references list, and concise operating rules. It respects token budget, is actionable, and organizes navigation one level deep.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; every line (routing table, references, operating rules) earns its place.

3 / 3

Actionability

Concrete, specific guidance is provided via an explicit routing table mapping intents to named skills plus actionable operating rules; for an instruction-only routing skill this is copy-ready direction.

3 / 3

Workflow Clarity

The flow is clear and unambiguous: classify by job-to-be-done, route via the table, then pull references; for a simple routing skill no destructive-operation checkpoints are needed.

3 / 3

Progressive Disclosure

A clear overview points to one-level-deep references through a well-signaled routing table and a supporting references list, with no nested indirection.

3 / 3

Total

12

/

12

Passed

Description

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

The description is brief and carries an explicit trigger but fails to state any concrete capabilities, leaving 'what this skill does' unspecified. Trigger coverage is narrow and somewhat generic within the Zoom domain.

Suggestions

Add concrete capabilities, e.g. 'Classifies Zoom requests by job-to-be-done and routes to the right implementation skill (OAuth, Meeting SDK, Video SDK, bots, debugging).'

Expand trigger terms to include natural variations users would say, such as 'Zoom integration', 'Zoom meeting app', 'Zoom SDK', or 'Zoom API'.

Combine what and when in one sentence: state the routing/classification action, then the 'Use when starting any Zoom work' trigger.

DimensionReasoningScore

Specificity

The description 'Use when starting Zoom work.' names no concrete actions or capabilities, matching the vague/abstract anchor rather than naming a domain and some actions.

1 / 3

Completeness

It provides an explicit 'Use when starting Zoom work' trigger (when) but omits any statement of what the skill does, so completeness is capped short of 3.

2 / 3

Trigger Term Quality

'Zoom work' is a phrase users might say, but coverage is thin and missing common variations like 'Zoom meeting', 'Zoom API', or 'Zoom SDK'.

2 / 3

Distinctiveness Conflict Risk

The Zoom framing is somewhat niche and distinct from non-Zoom skills, but 'starting Zoom work' is generic enough to overlap with multiple Zoom skills.

2 / 3

Total

7

/

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