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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.aider-desk/skills/theme-factory/SKILL.md

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly specifies the domain (AiderDesk UI themes), lists concrete implementation actions, and provides an explicit 'Use when' clause with natural trigger terms. It covers both technical specifics (SCSS, i18n) and user-friendly language (color scheme, dark mode, light mode), making it easy for Claude to select appropriately.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'defining SCSS color variables', 'registering theme types', and 'adding i18n display names'. These are precise, actionable steps rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (create new AiderDesk UI themes by defining SCSS color variables, registering theme types, adding i18n display names) and 'when' (explicit 'Use when' clause with multiple trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'theme', 'color scheme', 'customizing appearance', 'dark mode', 'light mode', 'SCSS color variables'. Good coverage of both technical and casual terms.	3 / 3
Distinctiveness Conflict Risk	Highly specific to AiderDesk UI theming with distinct technical triggers like 'SCSS color variables', 'registering theme types', and 'i18n display names'. Unlikely to conflict with general styling or other UI skills.	3 / 3
	Total	12 / 12 Passed

Implementation

55%

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

The skill has an excellent, actionable checklist for adding a new theme with clear file paths, code examples, and verification steps. However, it is severely undermined by the massive inline Color Variable Reference section that transforms a focused workflow skill into a monolithic reference document. The reference content should be extracted into a separate file, keeping the SKILL.md focused on the workflow.

Suggestions

Extract the entire 'Color Variable Reference' section (background layers, diff viewer, text hierarchy, border hierarchy, accent colors, status colors, button colors, input colors, agent colors, opacity conventions, global color applications) into a separate REFERENCE.md file and link to it with a single line like '**Color variable reference**: See [REFERENCE.md](REFERENCE.md)'

Remove explanatory context that Claude can infer from reading existing theme files, such as the detailed tables of where each variable is visible — a simple 'copy an existing theme and change hex values' instruction with a pointer to the reference file is sufficient

Consider adding a minimal concrete example showing 3-4 representative variable changes (e.g., bg-primary, text-primary, accent-primary) to illustrate the pattern without documenting every variable inline

Dimension	Reasoning	Score
Conciseness	The Color Variable Reference section is extremely verbose, spanning hundreds of lines documenting every CSS variable, its usage, and where it's visible. This is reference material that belongs in a separate file, not inline in the skill body. Claude doesn't need exhaustive tables of every variable — it can read the existing theme files. The checklist portion is reasonably concise, but the massive reference section dominates the document.	1 / 3
Actionability	The checklist provides concrete, specific steps with exact file paths, exact code snippets (SCSS import, JSON entries), and clear naming conventions. Each step tells Claude exactly what file to edit and what to add. The workflow of 'copy an existing theme and adjust values' is practical and executable.	3 / 3
Workflow Clarity	The 7-step checklist is clearly sequenced with logical ordering (choose name → create file → register in aggregator → register in types → add i18n → verify in UI → quality checks). Step 6 provides explicit verification, and step 7 includes a thorough quality checklist covering contrast, key surfaces, and interaction states.	3 / 3
Progressive Disclosure	The massive Color Variable Reference section (which constitutes the majority of the document) should be in a separate reference file, not inline. The skill is a monolithic wall of text mixing a concise workflow checklist with an exhaustive variable reference. No bundle files are provided to offload this content, and no external references are used to keep the main skill lean.	1 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: hotovo/aider-desk
Commit: e82a91f

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.