CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-ui-ux

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

64

Quality

75%

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

100%

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-organized deprecation notice that gives Claude concrete, criteria-based routing to the two canonical skills. As a simple redirect skill it is appropriately lean and actionable with nothing extraneous.

DimensionReasoningScore

Conciseness

The body is lean: a deprecation statement, two concrete redirect rules with specific criteria, and a short rationale — no padding and no explanation of concepts Claude already knows.

3 / 3

Actionability

Each redirect gives concrete, specific decision criteria (product/design context, UX guidance, design-system alignment, DESIGN.md vs. visual reference, screenshot capture, Visual Ralph verdict, pixel-diff), making routing fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose sole action — route to $design or $visual-ralph — is unambiguous with clear criteria, satisfying the simple-skill allowance.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references (none exist), and the content is well-organized into clear statements, meeting the under-50-line simple-skill allowance for a top score.

3 / 3

Total

12

/

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 signals deprecation and redirects to two canonical skills, but it lacks explicit 'when to use' trigger guidance, concrete action listing, and broader natural trigger terms. It reads more as a tombstone than an invocation description.

Suggestions

Add an explicit trigger clause (e.g., 'Do not use for new work; retained only for catalog/compatibility visibility') so the 'when' is stated, not implied.

Expand natural trigger terms beyond 'frontend UI/UX' to cover variations users actually say (interface, user experience, design system, styling, components).

If the skill must remain discoverable, state the one concrete action it performs (routing/redirecting to $design or $visual-ralph) rather than only labeling it a 'compatibility shim'.

DimensionReasoningScore

Specificity

Names the domain ('frontend UI/UX work') and a concrete redirect action ('use $design or $visual-ralph'), but lists no specific concrete actions the skill itself performs, so it stops short of the top anchor.

2 / 3

Completeness

It states clearly what the skill is ('Deprecated compatibility shim for frontend UI/UX work'), but there is no explicit 'Use when...' trigger clause for when to invoke it, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

'frontend UI/UX' are natural user terms, but coverage is thin — missing common variations like 'interface', 'user experience', 'design system', or 'styling' — and '$design'/'$visual-ralph' are invocation names rather than natural keywords.

2 / 3

Distinctiveness Conflict Risk

It occupies a specific niche and explicitly names the canonical alternatives, but the trigger 'frontend UI/UX work' overlaps heavily with the very skills it redirects to, leaving real conflict risk.

2 / 3

Total

8

/

12

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.