theme-factory

Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages. Ships 10 pre-set themes.

Quality

50%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/theme-factory/SKILL.md

Quality

Content

47%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 body is a catalogue stub: concise and well-structured, but it delegates all real functionality to an upstream GitHub repo without giving the agent an executable installation path or any theming instructions. It reads as an advertisement rather than an actionable skill.

Suggestions

Replace the vague "install the upstream bundle" instruction with a concrete, executable command (e.g., a git clone or copy step with the target skills-directory path).

Inline the core workflow — how to list and apply one of the 10 preset themes to an artifact — so the skill is usable without fetching the upstream repo.

Remove the duplicated description text and upstream URL from the body since both already appear in the frontmatter.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean with no concept over-explanation, but it duplicates the frontmatter description verbatim in "What it does" and repeats the upstream URL already present in the frontmatter, which could be trimmed.	4 / 5
Actionability	The only concrete command is `open https://...` to inspect the README; the operative instruction "install the upstream bundle into your active agent's skills directory" has no command or steps, and no guidance exists on actually applying themes.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream → install bundle → invoke by name or trigger phrase), but the central install step is undefined and no checkpoints are given, matching "rough sequence present but many gaps".	2 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/), and the body is organized into clear sections with one well-signaled, one-level-deep reference (the upstream URL); the gap is that disclosure is delegated entirely to an external repo rather than bundled files.	4 / 5
	Total	12 / 20 Passed

Description

53%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 states a clear, moderately specific capability with a distinct niche, but it omits any "Use when..." guidance and lacks synonym coverage, so it functions as a "what"-only description. Adding explicit trigger conditions and natural variations would round it out.

Suggestions

Append a "Use when..." clause (e.g., "Use when the user wants to restyle an artifact with a preset theme, palette, or font pairing") so the description answers both what and when.

Add natural synonym trigger terms such as "style", "color palette", "branding", and "look and feel" alongside "theme".

Name one or two more concrete actions (e.g., "generates CSS variable palettes and font pairings") to lift specificity beyond a single apply-theme action.

Dimension	Reasoning	Score
Specificity	"Apply professional font and color themes" is one concrete action with named artifact targets (slides, docs, reports, HTML landing pages) plus "Ships 10 pre-set themes", but it lists only a single action rather than several specific capabilities, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	The description clearly answers "what" (apply font and color themes, 10 pre-sets) but contains no "Use when..." clause; trigger phrases live only in a separate frontmatter `triggers` field, so "when" is at best weakly implied — capping completeness at 3 per the judging guideline.	3 / 5
Trigger Term Quality	Natural terms like "theme", "font and color themes", and the artifact names (slides, docs, reports, HTML landing pages) are present, but common user synonyms such as "style", "color palette", "branding", or "look and feel" are missing.	3 / 5
Distinctiveness Conflict Risk	Artifact theming is a distinct niche with specific triggers ("theme factory", "apply theme", "preset theme"), though generic design phrases like "design theme" carry minor overlap risk with other design-system or branding skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/theme-factory/SKILL.md
Commit: 1b47e60

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.