ui-ux-pro-max

This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.

Quality

75%

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-ux-pro-max/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 concise and well-structured with a clear workflow, but its actionability is undermined by a broken core tool: the bundled search.py hard-fails on every invocation because the referenced data/ui-reasoning.csv is missing and loaded unconditionally. Validation checkpoints are also absent.

Suggestions

Bundle the missing data/ui-reasoning.csv (or lazy-load it only for --design-system) so the documented search.py commands actually execute instead of crashing with FileNotFoundError.

Move the load_rules() call in main() inside the --design-system branch so --domain and --stack modes work even when the CSV is absent.

Add a validation/error-recovery checkpoint (e.g., verify the helper output is non-empty before synthesizing, and handle a missing CSV gracefully) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no explanation of concepts Claude already knows; sections, command blocks, and bullet lists each earn their place and assume Claude's competence.	5 / 5
Actionability	The commands appear copy-paste ready, but every documented invocation crashes: search.py unconditionally loads the referenced data/ui-reasoning.csv (line 237) which is absent from the bundle, so even --domain/--stack modes fail with FileNotFoundError, leaving the core workflow non-executable.	2 / 5
Workflow Clarity	A clear five-step sequence is present (infer shape, generate design system, pull targeted guidance, add stack guidance, synthesize), but there are no validation or error-recovery checkpoints and no guidance for handling the script's failure modes.	3 / 5
Progressive Disclosure	Good overview structure with one-level-deep references clearly signaled in the References section (USAGE.md, search.py, ui-reasoning.csv); the gap is that one referenced path (data/ui-reasoning.csv) does not exist in the bundle.	4 / 5
	Total	14 / 20 Passed

Description

88%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.

A strong, concrete description that explicitly pairs what the skill does with when to invoke it, using natural trigger terms and third-person voice. The only weakness is slightly less than comprehensive synonym coverage in trigger terms and minor overlap with generic frontend skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "design or review a UI", "create a landing page or dashboard", "choose colors or typography", "improve accessibility", "implement polished frontend interfaces" — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both: the "what" via the enumerated action list, and the "when" via the trigger clause "This skill should be used when the user asks to..."; voice is appropriately third person.	5 / 5
Trigger Term Quality	Natural phrases users would say ("design a UI", "create a landing page", "choose colors or typography", "improve accessibility") are present, but a few common synonyms/variations are missing, keeping it just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The UI/UX design niche with concrete triggers is mostly distinct from other skills, with only minor overlap risk against general frontend-development skills.	4 / 5
	Total	18 / 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: Galaxy-Dawn/claude-scholar
Path: skills/ui-ux-pro-max/SKILL.md
Commit: 6ed46da

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