ui-ux-pro-max

Catalog-only UI/UX Pro Max entry. The full upstream templates, data, and search workflow are not bundled in OpenDesign.

Quality

54%

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

63%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, honest about its catalog-only scope, and gives an unambiguous conditional workflow for both the installed and not-installed cases. Its main weaknesses are the repeated not-bundled disclaimer and an install step that defers to the upstream README instead of providing executable commands.

Suggestions

Replace the vague "install the upstream bundle into your active agent's skills directory" step with a concrete command (e.g., a git clone plus copy into the skills directory) rather than deferring to the upstream README.

Consolidate the catalog-only / not-bundled statement — currently repeated in "What it does", "Current OpenDesign scope", and "How to use" — into a single section to remove redundancy.

Restructure "How to use" as an explicit numbered decision list (check for upstream files → invoke if present; otherwise explain and ask about default guidance) so the conditional branches are scannable at a glance.

Dimension	Reasoning	Score
Conciseness	The body is short (~43 lines) and teaches nothing Claude already knows, but "the full upstream workflow is not bundled/not available locally" is repeated across "What it does", "Current OpenDesign scope", and "How to use", which could be consolidated into one statement. Mostly efficient with some tightening needed — not 4 due to this repetition, not 2 since each section is brief and adds distinct information.	3 / 5
Actionability	There is a concrete command (`open https://github.com/nextlevelbuilder/ui-ux-pro-max-skill`), explicit invocation guidance (by name or trigger phrase), and a fully specified fallback behavior, but the pivotal action — "install the upstream bundle into your active agent's skills directory" — has no executable command and defers entirely to the upstream README. Some concrete guidance, incomplete on the key step — not 4 given the missing install details, not 2 because the conditional fallback is specific.	3 / 5
Workflow Clarity	A clear conditional sequence is present: check whether upstream files exist ("If this SKILL.md is the only file under skills/ui-ux-pro-max/"), install and invoke by name or triggers if the full workflow is wanted, otherwise explain the catalog-only status and ask whether to continue with default design-system guidance. The directory check acts as a validation checkpoint; not 5 because the install path has no verification or recovery detail, not 3 because the decision logic and both branches are explicit.	4 / 5
Progressive Disclosure	At ~43 lines with no local bundle files (references/, scripts/, assets/ do not exist — verified) and well-organized sections (What it does / Current OpenDesign scope / Source / How to use), this matches the guideline that skills under 50 lines with no need for external references can score 5 on organization alone. The one external pointer (the upstream repo URL) is clearly signaled and one level deep.	5 / 5
	Total	15 / 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 is honest and explicit about what this entry is — a catalog-only pointer whose upstream workflow is not bundled — but it describes an absence rather than a capability, omits any 'use when' guidance, and relies on a separate triggers list that itself contains the ambiguous term "design patterns". It reads as accurate scaffolding rather than a well-formed skill description.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., "Use when the user asks for UI/UX patterns, usability heuristics, or design-system lookups") to satisfy the missing 'when' half of completeness.

State the entry's actual function in capability terms (e.g., "Provides discovery metadata and install instructions for the upstream ui-ux-pro-max UI/UX pattern library") instead of only describing what is absent.

Fold natural synonyms such as "user interface", "design system", and "usability" directly into the description rather than leaving them only in the frontmatter triggers list, and drop or qualify the ambiguous "design patterns" trigger.

Dimension	Reasoning	Score
Specificity	"Catalog-only UI/UX Pro Max entry... templates, data, and search workflow are not bundled" names the domain and concrete artifacts but states no actions the skill performs, matching 'names the domain but actions are minimal or generic'. It is not entirely vague (score 1), but it never lists the 1-2 concrete actions needed for score 3.	2 / 5
Completeness	The 'what' is clear — this is a metadata-only catalog entry with no local workflow — but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent, not 2 because 'what' is explicitly stated.	3 / 5
Trigger Term Quality	"UI/UX" is a term users naturally say, and the frontmatter triggers list ("ui ux patterns", "usability", "ux heuristics") is adjacent, but the description itself carries no trigger phrasing and misses common synonyms such as "user interface" or "design system". Not 4 because coverage has real gaps and "design patterns" is ambiguous with software design patterns.	3 / 5
Distinctiveness Conflict Risk	The UI/UX Pro Max niche is identifiable and "usability"/"ux heuristics" are domain-specific, but the trigger "design patterns" overlaps heavily with software design-pattern skills, creating overlap risk. Not 4 because that overlap is more than minor; not 2 because the entry's stated scope is genuinely distinct from generic document/code skills.	3 / 5
	Total	11 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: skills/ui-ux-pro-max/SKILL.md
Commit: 1b47e60

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.