CtrlK
BlogDocsLog inGet started
Tessl Logo

build-zoom-rest-api-app

Use when calling REST APIs.

40

Quality

40%

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

Quality

Content

65%

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

The body is concise and well-structured with genuinely useful domain-specific workflow guidance, but it lacks executable examples and ships broken reference paths that undermine navigation. Fixing the dead links and adding a small concrete API-call example would lift the weaker dimensions.

Suggestions

Correct the three dead reference paths (concepts/ and troubleshooting/ directories do not exist) to point at the real files under references/, or create those directories.

Add one short executable example (e.g. a server-to-server OAuth token request or a paginated meetings list call) so actionability reaches copy-paste readiness.

Insert an explicit validation checkpoint in the workflow (e.g. 'Confirm scopes and a successful test call before proceeding to batch/destructive operations') to add a feedback loop.

DimensionReasoningScore

Conciseness

The body is lean: a one-line intro, a tight six-step workflow with domain-specific guidance, and a references list, with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Guidance names concrete concerns (user-level vs account-level OAuth, pagination/retry/idempotency, a debug checklist) but provides no executable code, endpoint examples, or copy-paste snippets, leaning on reference files for the actual details.

2 / 3

Workflow Clarity

The six steps are clearly sequenced, but there is no explicit validate-then-proceed checkpoint; the debug step is reactive rather than a proactive validation gate, which matters for destructive/batch API operations.

2 / 3

Progressive Disclosure

The overview is clean and well-signaled with one-level-deep references, but three of the eight linked paths (concepts/api-architecture.md, concepts/authentication-flows.md, troubleshooting/token-scope-playbook.md) point to directories that do not exist in the bundle, breaking navigation.

2 / 3

Total

9

/

12

Passed

Description

15%

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 bare trigger clause with no statement of capability and no Zoom-specificity, making it both incomplete and highly conflict-prone. It reads more like a generic category label than a skill description.

Suggestions

Add a 'what' clause naming concrete actions, e.g. 'Builds application integrations that call Zoom REST APIs for meetings, recordings, users, and admin workflows.'

Include Zoom-specific trigger keywords so the skill is distinguishable from generic REST API skills.

Keep the 'Use when...' clause but combine it with the capability statement in third person to satisfy both completeness and specificity.

DimensionReasoningScore

Specificity

The description 'Use when calling REST APIs.' names a domain but lists no concrete actions or capabilities, matching the vague/no-actions anchor.

1 / 3

Completeness

It provides an explicit 'when' trigger but entirely omits 'what' the skill does (build Zoom REST API apps), so one of the two required answers is missing.

1 / 3

Trigger Term Quality

'REST APIs' and 'calling' are natural terms a user might say, but coverage is thin with no common variations (no 'Zoom', 'endpoints', 'HTTP requests', etc.).

2 / 3

Distinctiveness Conflict Risk

'Use when calling REST APIs' is extremely generic and never mentions Zoom, so it would conflict with many other API-calling skills.

1 / 3

Total

5

/

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: 3 missing

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.