CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hover

Use when adding, changing, or reviewing hovers or tooltips on VS Code widgets and UI elements, including buttons, actions, toolbars, lists, and trees. Covers custom versus native tooltips, hoverDelegate placement, HoverStyle, pointers, IHoverService delayed hovers, groupId, and shared instant-hover behavior across adjacent widgets.

Quality

93%

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

90%Weight 40%Scale 1-5

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

An excellent instruction-only skill body: dense with non-obvious VS Code-specific rules, concrete API mappings and code, and well-organized decision guidance. The only gaps are the absence of any verification step for checking hover behavior after changes, and the all-inline structure with repo-relative links that do not resolve outside the source tree.

Suggestions

Add a short verification step (e.g., how to confirm the shared delegate skips the delay on the second toolbar, or that the pointer renders on delayed element hovers) so implementers can check their wiring after a change.

Consider splitting the deep per-API grouping rules (delegate-based vs delayed-hover sections) into a reference file so SKILL.md reads as a shorter overview with well-signaled references.

Make the source-code and cross-skill links self-contained or verify their relative paths (hoverDelegate2.ts, ../accessibility/SKILL.md) resolve when the skill bundle is used outside the repository root.

DimensionReasoningScore

Conciseness

Lean and dense with non-obvious, repo-specific facts: 'Bare setupDelayedHover does not automatically add a pointer', "getDefaultHoverDelegate('element') ... does not enable instant hover", and 'This API excludes position and pointer overrides from its public options'. It never explains concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Decision tables map target to placement/pointer and surface to API, and copy-ready snippets cover the common cases: a shared createInstantHoverDelegate() passed to two toolbars, setupDelayedHover with groupId in lifecycle options, and a rich-row registration with HoverPosition.RIGHT and showPointer: true. Guidance is executable as written.

5 / 5

Workflow Clarity

The decision flow is clearly sequenced (custom vs native, placement/pointer, API choice, group sharing, ownership/a11y) with each choice made unambiguous by a table. It falls short of anchor 5 only because there is no verification guidance for confirming hover behavior (delay, pointer rendering, keyboard dismissal) after a change.

4 / 5

Progressive Disclosure

Well-organized sections with clear navigation, but everything is inline in a ~110-line document rather than split across an overview and reference files, and its relative links (e.g., hoverDelegate2.ts, ../accessibility/SKILL.md) point into the source tree rather than a self-contained bundle — they do not resolve as delivered. Good structure with minor organization gaps, matching anchor 4.

4 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 strong description: an explicit 'Use when...' trigger clause, a concrete scope statement, natural synonyms for the domain, and a highly specific niche. The only softness is that the stated actions ('adding, changing, or reviewing') are generic verbs, with specificity carried by the topic list instead.

DimensionReasoningScore

Specificity

Names the domain ('hovers or tooltips on VS Code widgets and UI elements'), explicit actions ('adding, changing, or reviewing'), and a concrete topic inventory ('custom versus native tooltips, hoverDelegate placement, HoverStyle, pointers, IHoverService delayed hovers, groupId, and shared instant-hover behavior'). It stays below anchor 5 because the stated actions are generic verbs rather than concrete operations like the anchor's 'fill forms, merge documents'.

4 / 5

Completeness

Explicitly answers both: the when ('Use when adding, changing, or reviewing hovers or tooltips on VS Code widgets and UI elements') and the what ('Covers custom versus native tooltips, hoverDelegate placement, HoverStyle, pointers, IHoverService delayed hovers, groupId'). Both are concrete, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

'hovers or tooltips' captures both natural synonyms users would say, and 'buttons, actions, toolbars, lists, and trees' enumerates the exact UI-element terms a user would name when asking for this. Matches the comprehensive-synonyms anchor; anchor 4 ('a few natural terms missing') does not fit.

5 / 5

Distinctiveness Conflict Risk

A clear niche (VS Code hover/tooltip implementation) claimed with API-specific terms (hoverDelegate, IHoverService, groupId) that no other skill would trigger on; minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/hover/SKILL.md

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.