CtrlK
BlogDocsLog inGet started
Tessl Logo

jsdoc

Full JSDoc format guide for TypeScript, covering @example formats (short, multi-line, multi-variant), tag usage (@default, @deprecated, what to avoid), documentation patterns for properties/enums/functions, and tag order.

74

Quality

91%

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

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.

An exemplar reference skill: concise, fully actionable with executable examples, and clearly organized into sections that mirror the description's promised scope. It also correctly positions itself as the deep reference tier relative to a lighter rule.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's TypeScript/JSDoc competence — it never explains what JSDoc is, and uses compact tables and fenced examples where every token earns its place.

3 / 3

Actionability

It provides concrete, copy-paste-ready JSDoc snippets for each case (short one-liner, multi-line, multi-variant, nested properties, functions) plus explicit correct/incorrect tables, leaving no ambiguity about what to write.

3 / 3

Workflow Clarity

As a single-purpose formatting reference it needs no multi-step validation loop; the 'Tag order' section gives an explicit 1–7 sequence and the Do/Do-not lists act as a clear checklist, satisfying the simple-skill allowance.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is intentionally the full reference ('Reach here when you need the full reference'), so the well-organized inline sections are appropriate; the pointer to the lightweight `jsdoc` rule signals the lighter-tier counterpart cleanly.

3 / 3

Total

12

/

12

Passed

Description

82%

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

A specific, well-scoped description with strong trigger terms and low conflict risk, written in third person. Its main weakness is the absence of an explicit 'Use when...' clause telling Claude when to invoke the skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing TypeScript JSDoc comments, or when the user asks about @example, @default, @deprecated, or tag formatting.'

Lead with the core capability before enumerating coverage, so the 'what' reads as a single clear action before the detail.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions/scope: '@example formats (short, multi-line, multi-variant), tag usage (@default, @deprecated, what to avoid), documentation patterns for properties/enums/functions, and tag order' — comprehensive and specific rather than vague.

3 / 3

Completeness

It clearly states what the skill does (full JSDoc format guide with enumerated coverage) but lacks any explicit 'Use when...' trigger clause, which caps completeness at 2 per the judging guideline.

2 / 3

Trigger Term Quality

It surfaces the natural terms a user would say when needing this skill — 'JSDoc', 'TypeScript', '@example', '@default', '@deprecated' — giving good coverage of the vocabulary users actually invoke.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply defined — a JSDoc format guide specifically for TypeScript — making it unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
kubb-labs/kubb
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.