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

57%

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 tidy, well-structured catalogue pointer that respects the token budget, but it provides almost no actionable content — it defers the actual install and the UI-constraint guidance to an external repo. As a standalone SKILL.md it informs but does not enable.

Suggestions

Add concrete install instructions (the actual copy/symlink or CLI command to place the upstream bundle in the skills directory) instead of 'Inspect the upstream README for exact paths.'

Include a minimal inline example of the constraints the skill enforces (e.g. a spacing or color-token rule snippet) so the skill is usable without round-tripping to GitHub.

Turn the 'How to use' section into an explicit, copy-pasteable sequence (install → verify the skill loads → invoke by name or trigger).

Dimension	Reasoning	Score
Conciseness	The body is short, sectioned, and lean; it does not explain concepts Claude already knows and nearly every line earns its place (the only minor redundancy is the 'What it does' section echoing the description).	3 / 3
Actionability	It describes rather than instructs: the only command is a trivial `open https://github.com/ibelick/ui-skills`, the actual install is deferred ('install the upstream bundle into your active agent's skills directory'), and it offers no executable guidance for the skill's real purpose (UI constraints).	1 / 3
Workflow Clarity	A loose sequence is present (advertise in Open Design → install upstream → invoke by name/trigger), but it is vague and pushes the real steps to the upstream README, so the single action is not fully unambiguous.	2 / 3
Progressive Disclosure	The body is under 50 lines with clean, well-organized sections and a single clearly-signaled one-level-deep external reference (the upstream GitHub URL); no bundle files exist to require deeper structure.	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 is a mediocre pointer: it identifies the UI-constraint domain and intent but stays abstract, offers no concrete capabilities, and lacks an explicit 'Use when...' trigger clause. It is distinguishable but not sharply differentiated from neighboring design skills.

Suggestions

Replace abstract language with concrete actions, e.g. 'Enforces spacing, color-token, and typography rules so multi-piece UI output stays visually coherent.'

Add an explicit trigger clause: 'Use when building or refining interfaces, applying a design system, or keeping UI output consistent across components.'

Surface natural trigger variations ('UI rules', 'design system constraints', 'consistent components') inside the description so the skill is less likely to collide with general frontend skills.

Dimension	Reasoning	Score
Specificity	It names the domain ('building interfaces', 'many small UI pieces') and a purpose ('guide agents', 'keeping output coherent') but lists no concrete actions — 'opinionated, evolving constraints' is abstract rather than a specific operation like enforcing spacing or color tokens.	2 / 3
Completeness	It states what the skill does (constraints to guide agents, keep output coherent) and implies when ('when building interfaces', 'Useful for...'), but lacks an explicit 'Use when...' clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The description text contains some natural terms a user would say ('interfaces', 'UI pieces', 'building interfaces'), but coverage is thin with no explicit trigger variations; the richer trigger list lives only in the separate frontmatter `triggers` field, not the description.	2 / 3
Distinctiveness Conflict Risk	The 'opinionated UI constraints' framing carves a recognizable niche, but 'building interfaces' is broad and could still overlap with other frontend/design-system skills without distinct triggers in the description itself.	2 / 3
	Total	8 / 12 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: a2ba3ee

Reviewed: 1 day 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.