setup-zoom-oauth

Use when setting up OAuth.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/zoom/skills/setup-zoom-oauth/SKILL.md

Quality

Content

72%

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

The content is a clean, lean overview that structures a planning workflow well and routes to one-level-deep references. Its weakness is actionability and workflow rigor: the steps name the right decisions but lack concrete selection criteria and explicit validation checkpoints.

Suggestions

Add concrete decision criteria to the abstract steps, e.g. for grant flow note when to use authorization-code vs. client-credentials vs. PKCE, so guidance is actionable rather than directional.

Insert an explicit verification checkpoint in the workflow, such as confirming the chosen scopes match the exact user flow before requesting tokens, to lift workflow clarity.

Optionally include a minimal concrete artifact (a sample token-storage shape or refresh call) so the token-handling step is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean — short scope bullets, a five-step workflow, and terse common-mistakes — with no padding and no explanation of OAuth concepts Claude already knows, matching the score-3 "every token earns its place" anchor.	3 / 3
Actionability	The workflow gives concrete decision dimensions (actor/tenant model, grant flow, minimum scopes, token storage/refresh) and the common-mistakes list is specific, but steps like "Choose the correct grant flow" stay high-level with no concrete criteria, endpoints, or examples, fitting the score-2 "some concrete guidance but incomplete" anchor rather than fully executable instruction.	2 / 3
Workflow Clarity	The five steps are clearly sequenced and step 5 gates reference routing on the prior steps being clear, but there are no explicit validation or verification checkpoints, matching the score-2 "sequence present but checkpoints missing or implicit" anchor rather than the score-3 anchor requiring explicit validation steps.	2 / 3
Progressive Disclosure	At under 50 lines the body is well organized into Scope, Workflow, Primary References, and Common Mistakes, and its references are one level deep and clearly signaled, satisfying the simple-skills note that well-organized sections can score 3.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 grammatically a valid trigger clause but is too thin: it names the OAuth domain yet omits Zoom, lists no concrete capabilities, and answers "when" more than "what." It reads as a placeholder rather than a fully specified skill description.

Suggestions

Name the target service explicitly, e.g. "Use when setting up OAuth for the Zoom API", so the trigger is distinctive and does not fire for unrelated OAuth setups.

Add concrete capabilities to the "what", e.g. "Configures Zoom OAuth app type, grant flow, scopes, and token refresh lifecycle.

Round out trigger terms with natural variations users say ("Zoom login", "Zoom token", "Zoom app credentials") to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "setting up OAuth" names a concrete domain and a broad action, but lists no specific capabilities (grant selection, scope planning, token refresh) — better than a score-1 "helps with documents" yet less comprehensive than the score-3 anchor that lists multiple concrete actions.	2 / 3
Completeness	It has an explicit "Use when" trigger (the "when"), but the "what" is reduced to the vague phrase "setting up OAuth" with no enumerated actions, so it does not clearly answer both halves like the score-3 anchor.	2 / 3
Trigger Term Quality	"OAuth" is a natural keyword a user would say, but the description omits "Zoom" and other common variations, matching the score-2 anchor of "some relevant keywords but missing common variations."	2 / 3
Distinctiveness Conflict Risk	"OAuth" names a defined niche, but because "Zoom" is omitted the trigger would fire for any OAuth setup and could overlap with other OAuth skills, fitting the score-2 "could still overlap with similar skills" anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/zoom/skills/setup-zoom-oauth/SKILL.md
Commit: 11c74d6

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.