CtrlK
BlogDocsLog inGet started
Tessl Logo

debug-zoom-integration

Use when isolating failures.

48

Quality

52%

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

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 body is concise and well-structured with a clear triage order, evidence checklist, and reference routing. It would benefit from explicit hypothesis-confirmation checkpoints and more concrete ranking guidance.

Suggestions

Add an explicit validation step in the triage workflow, e.g. "Confirm each hypothesis against requested evidence before ranking the next layer."

Specify how to rank hypotheses (e.g., by likelihood and by how cheaply evidence can confirm them) so the output step is actionable rather than abstract.

Optionally include a minimal example of a short fix plan + verification steps so the Output section is concrete rather than a list of labels.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no explanations of concepts Claude already knows; every section earns its place, matching the lean/efficient anchor.

3 / 3

Actionability

It gives concrete checklists ("Evidence To Request") and a triage sequence, but offers no executable commands or specific examples and leaves hypothesis ranking underspecified, matching the some-concrete-but-incomplete anchor.

2 / 3

Workflow Clarity

A clear numbered triage sequence and an Output section give a recognizable workflow, but there is no explicit validation checkpoint to confirm a hypothesis before ranking the next, matching the sequence-with-implicit-checkpoints anchor.

2 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and one-level-deep references to sibling skills, matching the guideline allowing a 3 for short well-organized skills without external bundle references.

3 / 3

Total

10

/

12

Passed

Description

32%

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 provides a valid trigger clause but is too vague to convey what the skill concretely does or to distinguish it from generic debugging skills. It needs the Zoom-integration domain and concrete actions.

Suggestions

Name the domain and concrete actions, e.g. "Isolates failures in Zoom integrations across auth, REST API, webhooks, and SDKs."

Expand trigger terms to natural phrases users say: "debug", "troubleshoot", "Zoom integration failing", or "error in Zoom".

Add an explicit "Use when..." clause naming Zoom-specific failure scenarios to reduce conflict with generic debugging skills.

DimensionReasoningScore

Specificity

The description only states "isolating failures" with no concrete actions or named domain, matching the vague/abstract anchor rather than the anchor that names a domain and some actions.

1 / 3

Completeness

It has an explicit "Use when" trigger but the "what does this do" half is effectively absent beyond the trigger, leaving one of the two required halves weak.

2 / 3

Trigger Term Quality

"isolating failures" is a relevant but narrow phrase missing common variations like "debug", "troubleshoot", or "error", so it has some keywords but incomplete coverage.

2 / 3

Distinctiveness Conflict Risk

"isolating failures" is extremely generic and would conflict with many other debugging or troubleshooting skills, matching the very-generic anchor.

1 / 3

Total

6

/

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