CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

theme-factory

Create new AiderDesk UI themes by defining SCSS color variables, registering theme types, and adding i18n display names. Use when adding a theme, creating a color scheme, customizing appearance, or implementing dark mode and light mode variants.

Quality

88%

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

77%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 well-executed procedural skill: the add-a-theme checklist is fully sequenced with verification and troubleshooting feedback loops, and the variable reference is app-specific knowledge Claude could not infer. The main structural weakness is that the large Color Variable Reference is inlined in SKILL.md rather than split into a references/ file, inflating context cost for every skill load.

Suggestions

Move the Color Variable Reference (background/text/border/accent/status/button/agent variable tables) into references/variables.md and keep a short summary table in SKILL.md, since no bundle files currently exist to absorb the ~130-line reference.

Include a minimal example .theme-<name> class snippet (a few variables with hex values) so the core artifact is templated rather than solely deferred to copying theme-dark.scss.

Trim the duplicated opacity guidance: the 'Color opacity suffix convention' table repeats percentages already stated in the status-color and bg-tier sections; a single table would suffice.

DimensionReasoningScore

Conciseness

Dense reference material with no padding and no explanation of concepts Claude already knows; every section adds app-specific knowledge. Minor over-explanation remains ('Practical way to ensure completeness' prose, and the opacity suffix table partially duplicating the status-variant semantics), so it fits the 4 anchor rather than 5's every-token-earns-its-place bar.

4 / 5

Actionability

Exact file paths, an `@use` SCSS snippet, an i18n JSON snippet, and a complete variable inventory make the guidance mostly executable. Minor gaps keep it below 5: no example SCSS theme class is shown (the skill defers to copying theme-dark.scss), and verification steps are manual UI actions rather than commands.

4 / 5

Workflow Clarity

A clearly sequenced 7-step checklist with an explicit verification step ('Confirm the new theme appears in the dropdown... whole UI updates'), a quality-check step (WCAG AA contrast, key surfaces, hover states), and a troubleshooting section mapping failure to fix ('Theme not showing up: missing @use import... missing entry in THEMES'). This matches the 5 anchor's explicit validation plus error-recovery feedback loops; the destructive/batch cap does not apply. Not 4 because feedback loops are explicit, not merely present.

5 / 5

Progressive Disclosure

No bundle files exist and the ~130-line Color Variable Reference is inlined in a 265-line SKILL.md instead of being split into a one-level-deep references/ file. Structure itself is good, but content that clearly belongs in a separate reference file is inline, matching the 3 anchor; it is not 4 because there are no well-signaled references at all.

3 / 5

Total

16

/

20

Passed

Description

92%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: it states three concrete actions that fully cover the skill's scope, pairs them with an explicit 'Use when...' trigger clause, and stays tightly scoped to AiderDesk theming. The only minor weakness is that a few natural trigger synonyms (e.g. 'styling', 'look and feel') are absent.

DimensionReasoningScore

Specificity

Lists multiple concrete, comprehensive actions ('defining SCSS color variables, registering theme types, and adding i18n display names') covering the full scope of the skill. Not 4 because coverage of the skill's actions is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (create AiderDesk themes via SCSS variables, type registration, i18n names) and 'when' ('Use when adding a theme, creating a color scheme...') with concrete trigger phrases, mirroring the score-5 anchor example. Not 4 because the 'when' clause is fully explicit, not merely adequate.

5 / 5

Trigger Term Quality

Natural user phrases like 'adding a theme', 'creating a color scheme', 'customizing appearance', and 'dark mode and light mode' give good coverage, but a few natural variants (e.g. 'styling', 'look and feel') are missing, matching the 4 anchor rather than the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific app and concrete artifacts ('AiderDesk UI themes', SCSS variables, theme types, i18n display names), giving a clear niche with distinct triggers and minimal conflict risk. The slightly broad 'customizing appearance' trigger is qualified by the app-specific context, keeping this at 5 rather than 4.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

hotovo/aider-desk

Path

.aider-desk/skills/theme-factory/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.