ui-skills-root

Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

Quality

70%

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/ui-skills-root/SKILL.md

Quality

Content

86%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 an exceptionally lean, well-structured routing skill with executable CLI commands and clear selection rules; its only weak spot is that a few protocol steps stay abstract rather than fully actionable.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept re-explanation or padding; every section (Protocol, CLI, Selection Rules) earns its tokens and assumes Claude's competence.	5 / 5
Actionability	Provides executable CLI commands and concrete selection heuristics, but some protocol steps ('decide if the task is UI-related', 'identify the likely category') remain high-level guidance rather than directly runnable actions.	4 / 5
Workflow Clarity	A clear 7-step numbered protocol sequences the work; being a non-destructive selection task it needs no validation loop, but no explicit checkpoints or feedback handling are present either.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and no need for external references, satisfying the simple-skill exception for a clean, navigable overview.	5 / 5
	Total	18 / 20 Passed

Description

55%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 covers both what and when and is reasonably distinct, but it relies on a single generic trigger term and offers only one concrete action, limiting keyword coverage and specificity.

Suggestions

Add concrete UI trigger phrases users naturally say (e.g., 'buttons', 'forms', 'layout', 'components', 'frontend') to broaden trigger term coverage.

List 2-3 specific capabilities (e.g., 'discover, select, and load the smallest relevant UI skill context') to lift specificity.

Tighten the 'what' to a clearer capability statement so it reads as more than a routing instruction.

Dimension	Reasoning	Score
Specificity	Names the UI domain and one concrete action ('select the smallest useful UI Skills context through the ui-skills CLI'), but stops at 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Has an explicit 'Use before UI-related work' trigger and a stated capability (select smallest context via the ui-skills CLI); the 'what' could be more specific but both halves are present.	4 / 5
Trigger Term Quality	Only the generic phrase 'UI-related work' is present; it omits the natural terms users actually say (button, form, layout, component, frontend).	2 / 5
Distinctiveness Conflict Risk	The routing-via-ui-skills-CLI framing gives it a distinct niche with only minor overlap risk against generic UI/frontend skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ibelick/ui-skills
Path: skills/ui-skills-root/SKILL.md
Commit: f5dd1de

Reviewed: 5 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.