CtrlK
BlogDocsLog inGet started
Tessl Logo

theme-factory

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

49

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/theme-factory/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is concise and well-organized with clear sectioning, but it functions as a thin catalogue pointer rather than an actionable skill body — it defers all real guidance to an external upstream repo and offers no executable theming instructions. Workflow steps for installing/invoking are only loosely sketched.

Suggestions

Replace or supplement the external-redirect instructions with at least one concrete, executable example of applying a preset theme to an artifact.

Turn the 'How to use' prose into an explicit numbered sequence (install upstream bundle -> verify path -> invoke by name or trigger).

Avoid duplicating the frontmatter description verbatim in 'What it does'; use that section for genuinely new context.

DimensionReasoningScore

Conciseness

The body is short and free of concept explanation padding, but it repeats the frontmatter description verbatim in 'What it does' and spends lines describing its own catalogue nature, so it could be tightened (anchor 2).

2 / 3

Actionability

It provides a specific upstream URL and an invocation mechanism, but offers no executable theming guidance — the actual skill content is deferred to the external repo, leaning toward 'describes rather than instructs' (between anchors 1 and 2).

2 / 3

Workflow Clarity

The single redirect-to-upstream action is outlined but the sequence (inspect README -> install bundle -> invoke by name) lacks explicit steps or checkpoints, fitting anchor 2 rather than a clean simple-skill 3.

2 / 3

Progressive Disclosure

The body is well under 50 lines, has clear organized sections, and needs no bundle files; the only reference is a clearly signaled external upstream URL, meeting the simple-skill bar for score 3.

3 / 3

Total

9

/

12

Passed

Description

50%

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 clearly communicates a focused theming skill and is concise, but it omits explicit "Use when..." trigger guidance and relies on a single broad action verb rather than enumerating concrete capabilities. Trigger coverage is decent but lacks common natural variations.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggering situations, e.g. 'Use when styling slides, docs, reports, or HTML pages with a consistent font and color scheme'.

Expand the action list beyond 'Apply' to concrete operations like 'pick, preview, and apply preset themes, or customize font/color tokens'.

Broaden trigger terms with natural user phrasings such as 'color scheme', 'font pairing', and 'brand styling'.

DimensionReasoningScore

Specificity

Names the theming domain and several concrete artifact types ("slides, docs, reports, and HTML landing pages") but only offers the single action "Apply... themes" rather than a list of distinct concrete actions, matching anchor 2 rather than 3.

2 / 3

Completeness

It states what the skill does but includes no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The triggers "apply theme", "design theme", "theme generator", and "preset theme" are reasonably natural, but coverage misses common user phrasings like "font", "color scheme", or "brand colors", landing at anchor 2.

2 / 3

Distinctiveness Conflict Risk

The design-system niche and theme-specific triggers are reasonably distinct, but "apply theme"/"design theme" could still overlap with general formatting or styling skills, fitting anchor 2 rather than 3.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.