ui-development

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

Quality

65%

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 content is an efficient, well-structured overview with concrete tool names and crisp rules, but its workflow lacks validation checkpoints and the core install/MCP steps are not fully executable. Referenced detail files are signaled but paths are incomplete and no bundle files are actually provided.

Suggestions

Add a validation/verification step to the registry-modification workflow (e.g. confirm the component still renders or run the project's UI tests before proceeding).

Provide the actual CLI install command and a concrete MCP `get_component` call example so the primary workflow steps are copy-paste executable.

Give referenced files full paths (e.g. `references/use-ui-registry.md`) and list the contents of the `rules/` directory instead of a generic pointer.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly rule-based with minimal concept explanation, but the "Activation Conditions" keyword list duplicates trigger info that belongs in the description, a minor instance of padding that could be trimmed.	4 / 5
Actionability	Concrete specifics are present (MCP tool names `mcp__redpanda-ui__search-docs`/`mcp__redpanda-ui__get_component`, the `ls src/components/redpanda-ui/` command, registry paths), but the core "Install components via CLI" and the MCP fetch step lack an executable command or call example, leaving minor gaps.	4 / 5
Workflow Clarity	A rough sequence exists (fetch docs, check existing components, then apply rules), but there are no validation checkpoints, and the "WHEN MODIFYING REGISTRY COMPONENTS" workflow — a risky edit operation — has no verify/test step, which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body is structured as a lean overview with a Quick Reference table and a `rules/` pointer representing one-level-deep references, but the referenced .md files lack directory paths and "See `rules/` directory" is generic, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 identifies the domain and technology stack but lacks an explicit use-when trigger clause and lists only one action. It is distinguishable thanks to the Redpanda Registry specificity, yet trigger guidance and action breadth keep it from the top tier.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when building UI components or pages with the Redpanda Registry, or when the user mentions UI, frontend, or the registry.'

List multiple concrete actions instead of the single 'Build UI' (e.g. install, compose, customize, and style registry components).

Include common synonyms users would say (frontend, design system, interface) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	"Build UI with Redpanda Registry components, Tailwind v4, and accessibility best practices" names the domain and supplies concrete technology specifics, but offers only a single generic action ("Build UI") rather than multiple distinct actions, so it sits between the domain-only and comprehensive-coverage anchors.	3 / 5
Completeness	The description clearly states what it does (build UI with the registry stack) but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms users would say are present ("UI", "Registry", "component"), giving good keyword coverage, though common synonyms such as "frontend", "interface", or "design system" are missing.	4 / 5
Distinctiveness Conflict Risk	The "Redpanda Registry" niche is specific and largely distinct from generic skills, but the broad "Build UI" phrasing leaves minor overlap risk with general frontend skills.	4 / 5
	Total	14 / 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: 2deda0a

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