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 content is a well-organized but thin catalogue entry that redirects to an upstream repository; it is concise and cleanly structured but lacks concrete executable guidance for actually applying themes and offers no real workflow with validation.

Suggestions

Replace the `open https://…` browser command with the actual concrete step to install the upstream bundle (e.g., a clone/copy command and the target skills-directory path).

Provide at least one executable example of applying a preset theme to an artifact, or explicitly justify why guidance is deferred to the upstream README.

Spell out the install-then-invoke workflow as numbered steps with a verification checkpoint (e.g., confirm the skill appears in the agent's skill list before invoking).

Dimension	Reasoning	Score
Conciseness	The body is short and lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only redundancy is the 'What it does' section repeating the frontmatter description, a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	The only concrete command is `open https://…` which merely opens a webpage rather than performing the task, and 'install the upstream bundle' / 'invoke by name or trigger phrases' are high-level hints missing the specific executable steps, matching the 'minimal concrete guidance' anchor.	2 / 5
Workflow Clarity	A rough sequence is present (advertise → install upstream → invoke by name/trigger) but the steps are poorly defined with no specific install command and no validation checkpoints, fitting the 'rough sequence present but many gaps; validation absent' anchor.	2 / 5
Progressive Disclosure	No bundle files exist, so scoring rests on organization: the body is well-structured with clear sections (What it does, Source, How to use) and under 50 lines, but navigation to detail goes to an external upstream URL rather than clearly signaled one-level-deep local references, a minor gap.	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 is third-person, concise, and clearly states the skill's purpose and target artifact types, but it lacks an explicit 'Use when…' trigger clause and only describes a single action.

Suggestions

Add a 'Use when…' clause naming concrete trigger phrases (e.g., 'Use when applying font/color themes to slides, docs, reports, or HTML pages, or when the user asks for preset themes or design styling').

Expand the action list beyond 'apply' to cover what the themes touch (e.g., sets typography, palette, spacing) so specificity reaches comprehensive coverage.

Include common synonyms users say ('design theme', 'preset theme', 'branding/styling') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (font/color themes) and target artifacts (slides, docs, reports, HTML landing pages) but offers only one concrete action ('Apply … themes') plus the count '10 pre-set themes', which matches the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when…' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 even though the 'what' is clear.	3 / 5
Trigger Term Quality	The description contains relevant natural keywords ('font', 'color themes', 'themes', 'slides', 'docs', 'HTML landing pages') but omits common variations a user might say such as 'design', 'branding', 'styling', or 'preset', fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'Apply professional font and color themes' carves a reasonably distinct theming niche with low conflict risk, with only minor overlap against generic design/branding skills, matching the 'mostly distinct; minor overlap' anchor.	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: d4138ea

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.