ui-skills

Opinionated, evolving constraints to guide agents when building interfaces. Useful for keeping output coherent across many small UI pieces.

Quality

53%

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

Quality

Content

61%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 lean, well-structured catalogue entry that points to an upstream repo rather than containing the skill's actual guidance. It is concise and navigable but not directly actionable: the real install/usage steps are deferred to the external README.

Suggestions

Replace the `open <url>` placeholder with the concrete install command (or at least the exact target path) instead of deferring to the upstream README.

Tighten the 'How to use' paragraph by removing the meta-explanation of what the catalogue entry does in OpenDesign.

If the upstream assets/scripts/references are intended to be used locally, bundle or summarize the core rules inline so the skill is self-contained rather than a pure redirect.

Dimension	Reasoning	Score
Conciseness	The body is short and well-sectioned, but the 'How to use' prose mildly over-explains ('advertises the skill in OpenDesign so the agent discovers it during planning') and repeats the description in 'What it does', fitting 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	The only executable command is `open https://github.com/ibelick/ui-skills`; the actual install steps are deferred ('inspect the upstream README for exact paths'), so guidance is concrete but incomplete, matching 'Some concrete guidance but incomplete; missing key details'.	3 / 5
Workflow Clarity	A rough sequence exists (install upstream bundle, then invoke by name/trigger) but the key install step is undefined and points elsewhere, leaving checkpoints/steps implicit rather than clearly sequenced.	3 / 5
Progressive Disclosure	The body is well-organized into clearly labeled sections (What it does, Source, How to use) with a clearly signaled single external reference, though the reference is an upstream URL rather than a one-level-deep bundle file.	4 / 5
	Total	14 / 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 names its domain but relies on abstract language with no concrete actions and no explicit 'use when' trigger guidance. It is serviceable but lacks the specificity and trigger completeness of a strong description.

Suggestions

Replace abstract phrases ('guide agents', 'keeping output coherent') with concrete capabilities the skill performs, e.g. 'apply layout/spacing/typography constraints', 'check UI pieces against a ruleset'.

Add an explicit 'Use when...' clause stating the situations that should trigger this skill (e.g. 'Use when generating or reviewing many small UI components that must stay visually consistent').

Include more natural user-facing trigger terms and synonyms (e.g. 'UI consistency', 'design rules', 'component styling') to improve discoverability.

Dimension	Reasoning	Score
Specificity	It names the domain ('building interfaces', 'UI pieces') but the only 'actions' are abstract ('guide agents', 'keeping output coherent') with no concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It gives a clear 'what' (opinionated constraints to guide agents building interfaces) but provides no explicit 'when'/'Use when' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant terms ('interfaces', 'UI pieces', 'constraints') appear but common natural variations a user would say are missing, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The 'opinionated constraints for coherent UI across small pieces' framing is somewhat specific but 'building interfaces' is broad enough to overlap with other UI/design skills, matching 'Somewhat specific but could still overlap'.	3 / 5
	Total	11 / 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/ui-skills/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.