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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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-sequenced theming guide with strong validation checkpoints and troubleshooting feedback loops. Its main weakness is that the large variable reference is kept inline rather than offloaded to a one-level-deep reference file, and some reference tables carry minor redundancy.

Suggestions

Move the Color Variable Reference (background/text/border/accent/status/button tables) into a references/ file (e.g. COLOR-VARIABLES.md) and link to it from SKILL.md to improve progressive disclosure.

Trim redundant opacity-suffix alternates (e.g. the "19"/"4d"/"7f" "(alternate)" rows) and remove or condense the "Currently not directly used" input-colors note to tighten conciseness.

Consider condensing the per-status 7-variant suffix list into a single compact convention block rather than enumerating each variant inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and domain-specific, but the Color Variable Reference and opacity-suffix table contain redundancy (e.g. "19 ≈ 10% — subtle (alternate)") and marginal notes ("Currently not directly used" for input colors) that could be trimmed; not every token earns its place as the score-3 anchor requires.	2 / 3
Actionability	It gives exact file paths, an executable `@use 'theme-<name>.scss';` snippet, a concrete i18n JSON example, and a parameterized but copy-paste-ready workflow — fully actionable rather than the pseudocode/vague score-1/2 anchors.	3 / 3
Workflow Clarity	A clear 7-step sequenced checklist with explicit validation ("Verify in the UI", "Quality checks" aiming for WCAG AA) and a Troubleshooting feedback loop for error recovery, matching the score-3 anchor.	3 / 3
Progressive Disclosure	Content is well-sectioned but the ~135-line Color Variable Reference is inline in SKILL.md with no bundle/reference files present to split it into; the skill is well over 50 lines so the simple-skill exception does not apply, keeping it at score 2 rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

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.

A strong, third-person description that pairs concrete actions with explicit natural-language triggers, cleanly answering both what the skill does and when to use it. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	"defining SCSS color variables, registering theme types, and adding i18n display names" lists multiple specific concrete actions, matching the score-3 anchor rather than the single-action score-2 anchor.	3 / 3
Completeness	It explicitly states both what ("Create new AiderDesk UI themes by defining SCSS color variables, registering theme types, and adding i18n display names") and when ("Use when adding a theme, creating a color scheme...") with an explicit trigger clause.	3 / 3
Trigger Term Quality	"adding a theme, creating a color scheme, customizing appearance, or implementing dark mode and light mode variants" covers natural phrases a user would say; it is not jargon-only (which would be score 1) nor missing common variations (score 2).	3 / 3
Distinctiveness Conflict Risk	"AiderDesk UI themes" and SCSS/i18n-specific triggers carve out a clear niche unlikely to fire for unrelated skills; it is far more specific than the generic score-1/2 examples.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: hotovo/aider-desk
Commit: 05579a4

Reviewed: 3 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.