ux-theming

VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC/focus compliance.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 highly actionable, well-organized reference skill: executable code, exact file paths, and decision tables for what would otherwise be tribal knowledge. It is a task-indexed reference rather than a sequenced workflow, and a small amount of duplication and table bulk keep conciseness and progressive disclosure at the second-highest anchors.

Suggestions

Drop the opening line ('This skill covers color registration, CSS variable usage...') — it restates the frontmatter description without adding new information.

Consider moving the color-category table (§2) and/or the hardcoded-vs-correct table (§7) into a references/ file, keeping a one-line pointer in SKILL.md to reduce always-loaded tokens.

Add a short ordered 'adding a new themed widget' sequence (register color → use via asCssVariable/defaultStyles → verify focus + HC behavior) so the task-indexed sections also serve as a workflow.

Dimension	Reasoning	Score
Conciseness	Dense, tabular content that assumes competence (the hardcoded-vs-correct table, the color-category table) with no padding explaining basics Claude already knows; the opening line duplicates the frontmatter description and §3's conversion example could be trimmed, so it is not a 5.	4 / 5
Actionability	Copy-paste-ready code throughout: a complete registerColor snippet with all four theme types, CSS var() usage, the getButtonStyles override pattern, and named default-style objects with exact file paths. Examples cover the common cases (register, consume in CSS, style a widget, focus, HC overrides).	5 / 5
Workflow Clarity	Sections are indexed by task intent (register → use in CSS → widget styles → focus → HC) so lookup is unambiguous, and no destructive or batch operations exist to trigger the 3-cap; however there is no explicit end-to-end sequence or validation checkpoints for adding a new themed widget, so it does not reach the sequence-plus-feedback-loops of a 5.	4 / 5
Progressive Disclosure	A well-organized single file with clearly signaled pointers to the ux-css-layout skill and the design-tokens instructions file for size concerns, and no buried or nested references; at ~155 lines the color-category and hardcoded-values tables could arguably move to a reference file, so it is not a 5.	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: third-person, concise, with a clear VS Code theming niche and an explicit multi-trigger 'Use when' clause. The what-clause leans on topic nouns rather than action verbs, which is the only thing keeping specificity from the top anchor.

Dimension	Reasoning	Score
Specificity	Concrete actions are named ('registering colors', 'styling widgets with theme tokens', 'ensuring HC/focus compliance'), matching the 'several specific actions with minor gaps' anchor; the what-clause is a list of topics rather than full verb-phrases, keeping it below the comprehensive coverage of a 5.	4 / 5
Completeness	It explicitly answers both what ('VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support') and when, with three concrete trigger phrases in the 'Use when...' clause; the when-clause is fully explicit rather than weakly implied, so it is not a 4.	5 / 5
Trigger Term Quality	Natural keywords a VS Code contributor would say ('theming', 'color tokens', 'widget styles', 'focus indicators', 'high-contrast', 'HC') are present with good coverage; a few natural synonyms like 'theme colors' or 'CSS variables' are missing, so it does not reach comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	A clear VS Code theming niche with distinct triggers, but 'color tokens' slightly overlaps with the sibling ux-css-layout design-token skill referenced in the body, so minor overlap risk keeps it below 5; it is far more distinct than the broad anchor 3 examples.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: .github/skills/ux-theming/SKILL.md
Commit: b0258bc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.