CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

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

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

The skill delivers a concrete, well-sequenced workflow with strong verification and troubleshooting, but bundles a large color-variable reference directly in SKILL.md instead of splitting it into a one-level-deep reference file. Extracting that reference would improve both conciseness and progressive disclosure.

Suggestions

Move the 'Color Variable Reference' tables (background, text, border, accent, status, button, agent) into a separate references/COLOR-VARIABLES.md and link to it from SKILL.md to improve progressive disclosure and reduce token load.

Add a minimal copy-paste SCSS theme skeleton (the full set of `--color-*` variable names with placeholder hex values) so the core 'define the SCSS variables' step is fully executable without opening another file.

Remove the duplicated 'copy an existing theme' guidance (stated in both the Definition format section and step 2) to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly efficient and domain-specific, but it inlines ~140 lines of color-variable reference tables that inflate the SKILL.md token budget, plus minor repetition ('Best workflow: copy an existing theme' and 'Start by copying a similar theme').

3 / 5

Actionability

Provides concrete file paths, an executable `@use 'theme-<name>.scss';` snippet, and an i18n JSON example, but delegates the core SCSS definition to 'copy an existing theme' without a copy-paste SCSS skeleton.

4 / 5

Workflow Clarity

A clear 7-step numbered checklist is sequenced with an explicit verification step (verify in Settings dropdown) and a troubleshooting section providing error-recovery feedback loops.

5 / 5

Progressive Disclosure

Sectioning is clear, but no bundle/reference files exist and the large color-variable reference — material that belongs in a separate file — is inlined, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

15

/

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.

The description is specific, well-scoped, and explicitly pairs capabilities with natural 'Use when' trigger phrases in third-person voice. It is a strong, low-conflict description with only minor room to add a few more natural phrasings.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'defining SCSS color variables, registering theme types, and adding i18n display names' — giving comprehensive coverage of what creating a theme entails.

5 / 5

Completeness

Clearly answers 'what' (Create new AiderDesk UI themes by ...) and 'when' (Use when adding a theme, creating a color scheme, ...) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user-facing terms are well covered ('adding a theme, creating a color scheme, customizing appearance, or implementing dark mode and light mode variants') with useful synonyms, though no file extensions or a few additional phrasings ('skin', 'UI colors') are present.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific AiderDesk UI theme niche with distinct triggers ('AiderDesk UI themes', 'dark mode and light mode variants'), minimizing overlap with unrelated skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
hotovo/aider-desk
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.