CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ux-theming

VS Code theming, color tokens, composited surfaces, interaction-state precedence, and high-contrast support. Use when styling widgets, changing hover/focus/selection, or validating rendered theme states.

Quality

85%

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

82%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.

A dense, highly actionable reference skill with executable code patterns, concrete token/file tables, and unusually thorough validation checklists for interaction-state testing. Its weaknesses are modest: some repetitive and over-long prose around focus/hover semantics, and a very detailed HC contract section that could be split into a reference file.

DimensionReasoningScore

Conciseness

Nearly all content is repo-specific knowledge Claude cannot know (file paths, token names, defaultStyles names, HC rules) with no padding of basic concepts, but some long lawyerly paragraphs and repeated focus-vs-hover separation across sections 3, 5, and the HC contract could be tightened.

4 / 5

Actionability

Fully executable guidance throughout: a complete registerColor call with all four theme defaults, CSS-variable usage, defaultStyles/getButtonStyles widget patterns, focus-visible and HC box-shadow CSS, a copy-paste-ready ARIA state-precedence CSS block, and a hardcoded-vs-correct values table covering the common cases.

5 / 5

Workflow Clarity

Content is topic-organized rather than a sequenced pipeline, but explicit validation checkpoints are present (the state-matrix checklist of rest/hover/focus/combined states, the Testing Rendered Interaction States section, "Validate a state matrix rather than isolated screenshots"), leaving only the minor gap of no end-to-end order for adding a new themed widget.

4 / 5

Progressive Disclosure

Good structure with numbered sections, tables, and clearly signaled one-level-deep external links (ux-css-layout SKILL.md and an inline anchor); no bundle files exist, and the ~60-line high-contrast interaction-state contract is detailed enough that it could arguably live in a separate reference file, keeping this at the minor-organization-gaps anchor.

4 / 5

Total

17

/

20

Passed

Description

83%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 that explicitly covers both what the skill does and when to use it, with concrete, natural trigger phrases and a well-scoped VS Code niche. The main weaknesses are the noun-phrase rather than action-verb capability list and a few missing synonyms (e.g., CSS variables, contrast, accessibility).

DimensionReasoningScore

Specificity

Lists several specific capabilities ("VS Code theming, color tokens, composited surfaces, interaction-state precedence, and high-contrast support") plus concrete trigger actions ("styling widgets, changing hover/focus/selection, or validating rendered theme states"), but the 'what' is phrased as topic nouns rather than comprehensive verb-form actions, matching the minor-gaps anchor rather than full coverage.

4 / 5

Completeness

Explicitly answers both parts: the 'what' is a concrete topic list and the 'when' is an explicit "Use when styling widgets, changing hover/focus/selection, or validating rendered theme states" clause with three concrete trigger phrases, matching the both-answered-with-triggers anchor.

5 / 5

Trigger Term Quality

Natural developer phrases like "styling widgets", "hover", "focus", "selection", "theming", and "high-contrast" are present and would be said by users needing this skill, though common synonyms such as "CSS variables", "theme colors", or "contrast/accessibility" are missing.

4 / 5

Distinctiveness Conflict Risk

"VS Code theming" scopes a clear niche with distinct triggers, but the sibling ux-css-layout skill covers adjacent styling concerns, so "styling widgets" carries minor overlap risk with a closely related skill.

4 / 5

Total

17

/

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: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/ux-theming/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.