CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-ui-ux

Deprecated compatibility shim for frontend UI/UX work; use $design or $visual-ralph

54

Quality

60%

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/frontend-ui-ux/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-structured deprecation shim that gives clear, actionable routing to two canonical skills with concrete triggering criteria. It scores solidly across all dimensions, held just below top marks by minor redundancy and a bare trailing placeholder.

DimensionReasoningScore

Conciseness

The body is a lean routing notice with two clear redirect rules; the final paragraph ("This file exists only to preserve...") restates the deprecation rationale already implied by the opening, a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

It names exact skills to invoke (`$design`, `$visual-ralph`) with concrete triggering criteria ("product/design context", "approved generated/static/live-URL visual reference"), giving mostly executable routing guidance with only minor gaps.

4 / 5

Workflow Clarity

As a simple single-purpose routing skill it presents two unambiguous decision branches with clear criteria; the simple-skill exception applies, but the bare `{{ARGUMENTS}}` line is a minor structural gap keeping it just below 5.

4 / 5

Progressive Disclosure

Under 50 lines with no external file references needed (it points to other skills, not bundle files) and well-organized sections, satisfying the simple-skill exception; the trailing placeholder line is the only minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

45%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 clearly signals deprecation and routes to two named alternatives, but it lacks concrete capability actions, a 'Use when...' trigger clause, and natural trigger-term variants, leaving it around the midpoint of the scale.

Suggestions

Add an explicit trigger clause (e.g. 'Use when...') even for a deprecated shim, or state the deprecation more concretely so completeness is not capped at 3.

Include natural trigger-term variants users say ("design", "visual reference", "mockup", "pixel-diff") to lift trigger_term_quality.

Clarify the single concrete action the skill performs (e.g. 'Routes frontend UI/UX requests to $design or $visual-ralph') to improve specificity.

DimensionReasoningScore

Specificity

Names the domain ("frontend UI/UX work") but offers only minimal, generic actions — the description is a redirect ("use $design or $visual-ralph") rather than a list of concrete capabilities, matching the 'names the domain but actions are minimal' anchor.

2 / 5

Completeness

It states a clear 'what' ("Deprecated compatibility shim for frontend UI/UX work") but provides no 'Use when...' or equivalent explicit trigger guidance, so per the rubric cap it stays at 3.

3 / 5

Trigger Term Quality

"frontend UI/UX work" is a phrase users might naturally say, but the description omits common variations and synonyms (e.g. "design", "visual reference", "mockup"), so it falls at the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"frontend UI/UX work" is broad and overlaps heavily with the very alternatives it names ($design, $visual-ralph), placing it at 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.