ui-development

Build UI with Redpanda Registry components, Tailwind v4, and accessibility best practices.

Quality

61%

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 ./frontend/.claude/skills/ui-development/SKILL.md

Quality

Content

68%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 well-organized, concise, and mostly actionable, with clear progressive-disclosure pointers via the Quick Reference table. Its weakest point is workflow clarity: the build workflow is shallow and lacks a validation checkpoint for the risky operation of modifying synced registry components.

Suggestions

Add an explicit validation/verification step to the build workflow (e.g. confirm the component renders and passes existing tests before proceeding), since modifying synced registry components is a destructive/risky operation.

Replace the vague "Install components via CLI" rule with the actual CLI command so the guidance is fully copy-paste ready.

Add the missing build step to the Workflow section so the fetch → check → install → build sequence is complete rather than stopping at "check existing components".

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (Quick Reference table, terse ALWAYS/NEVER lists), with only minor explanatory prose in the "WHEN MODIFYING" section that could be trimmed; this fits the level-4 anchor rather than the fully lean level-5.	4 / 5
Actionability	Provides concrete, executable guidance (MCP tool names, `ls src/components/redpanda-ui/`, `git grep '\[upstream\]'`, a numbered modify procedure) with a minor gap — "Install components via CLI" names no actual command — matching level 4 rather than the fully copy-paste-ready level 5.	4 / 5
Workflow Clarity	The Workflow section lists a sequence (fetch docs, check existing components) but has no validation checkpoint, and modifying synced registry components is a risky operation without an explicit verify step, so per the feedback-loop cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Good structure with a Quick Reference table mapping actions to one-level-deep rule files and clear pointers to `rules/` and `registry-upgrade.md`; it is not level 5 because no bundle files actually exist to split content into, so some referenced paths cannot be verified.	4 / 5
	Total	15 / 20 Passed

Description

53%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 states what the skill does and names a specific tech niche, but omits any explicit "Use when..." trigger guidance, which caps its completeness and leaves its trigger-term coverage at a mid level. Adding a trigger clause with natural synonyms would lift the two weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when building or modifying UI with the Redpanda Registry, or when the user mentions design system, frontend, or registry components."

Add natural synonyms users actually say ("frontend", "design system", "pages") to broaden trigger-term coverage beyond "UI", "registry", and "components".

Dimension	Reasoning	Score
Specificity	Names the domain ("Build UI") plus concrete tech ("Redpanda Registry components", "Tailwind v4", "accessibility best practices"), but it is a single action rather than a comprehensive list of concrete actions, matching the level-3 anchor rather than 4 which requires several specific actions.	3 / 5
Completeness	Provides a clear "what" (build UI with the Registry, Tailwind v4, and accessibility practices) but has no "Use when..." clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Contains natural terms users would say ("UI", "registry", "components") but misses common variations such as "frontend" and "design system", fitting the level-3 anchor of relevant keywords with missing synonyms rather than the fuller coverage of level 4.	3 / 5
Distinctiveness Conflict Risk	The Redpanda Registry + Tailwind v4 + accessibility niche is mostly distinct with only minor overlap risk against generic frontend skills, matching the level-4 anchor; it is not level 5 because trigger phrases are absent, leaving slightly higher conflict risk.	4 / 5
	Total	13 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: redpanda-data/console
Path: frontend/.claude/skills/ui-development/SKILL.md
Commit: 60125ec

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.