ui-ux-pro-max

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agent/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-structured and highly actionable, with a clear step-by-step workflow, copy-paste commands, lookup tables, and a delivery checklist. Its weaknesses are redundancy (duplicated rules/checklist content and an unnecessary Python-install section), internal inconsistency with the frontmatter counts, and a broken reference layer — the data CSVs the whole search scheme depends on are missing from the bundle.

Suggestions

Ship the data/ directory (all domain and stack CSVs plus ui-reasoning.csv) or document that it must be fetched separately, since every command in the skill depends on it.

Merge the overlapping 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' sections into one reference file (or a single checklist), and drop the Python installation instructions — Claude already knows how to check for and install Python.

Fix the asset-count mismatch with the description (67 vs 50 styles, 96 vs 21 palettes) so the skill's own numbers agree.

Dimension	Reasoning	Score
Conciseness	Mostly dense and useful (command tables, domain/stack mappings), but the Prerequisites section re-explains checking and installing Python — something Claude already knows — and the 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' sections overlap heavily (emoji icons, cursor-pointer, hover feedback, and contrast each appear twice). This matches anchor 3 (mostly efficient but with unnecessary explanations and tightening opportunities) rather than anchor 4.	3 / 5
Actionability	Guidance is concrete and copy-paste ready: exact commands with flags ('python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"'), a needs-to-domain lookup table, and a fully worked example workflow. Not a 5 because the referenced data files (data/*.csv per core.py and 'ui-reasoning.csv') are absent from the bundle, so the commands as shipped would fail without them.	4 / 5
Workflow Clarity	The workflow is clearly sequenced (analyze requirements → generate design system → supplement with domain searches → stack guidelines) with an explicit worked example and a Pre-Delivery Checklist acting as a final validation checkpoint. Not a 5 because there are no feedback loops for error recovery (e.g. what to do when a search returns no matches beyond 'try different keywords').	4 / 5
Progressive Disclosure	The on-demand search-script pattern is good progressive disclosure in principle, but judged against the actual bundle the referenced paths do not resolve: core.py expects a data/ directory of CSVs and the body cites 'ui-reasoning.csv', none of which are present, so navigation is broken at the top level. Additionally, ~80 lines of 'Common Rules' and 'Pre-Delivery Checklist' are inlined in SKILL.md where they belong in a reference file. This fits anchor 3 (some structure, could be better organized) better than anchor 4.	3 / 5
	Total	14 / 20 Passed

Description

48%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 communicates scope through concrete asset counts but reads as a contents listing rather than a capability statement: no actions, no 'Use when' trigger guidance, and inventory counts (50 styles, 21 palettes) that contradict the body (67 styles, 96 palettes), which undermines its reliability. It is distinguishable from other skills but under-serves both trigger matching and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to design, build, restyle, or review web or mobile UI, pick fonts or color palettes, or needs UX best practices.'

Replace the asset-count inventory with concrete actions (e.g. 'Generates complete design systems — style, colors, typography, effects — and searches UX/chart/stack guidelines for any product type').

Reconcile the counts in the description with the body's numbers (50 vs 67 styles, 21 vs 96 palettes) so the description is accurate.

Dimension	Reasoning	Score
Specificity	The description names the domain ("UI/UX design intelligence") and lists asset inventory counts ("50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks") but contains no concrete actions or verbs — it says what the skill contains, not what it does. It sits between anchor 2 (domain named, actions minimal/generic) and anchor 3 (1-2 concrete actions); it never states any action, so it stays at 2 rather than 3.	2 / 5
Completeness	A 'what' is present (design intelligence with enumerated asset categories) but there is no 'Use when...' clause or any trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and informative, not vague.	3 / 5
Trigger Term Quality	"UI/UX design", "styles", and "font pairings" are terms users would naturally say, but very common phrasings like "colors", "theme", "landing page", "dashboard", or "design system" are missing. This matches anchor 3 (some relevant keywords but missing common variations/synonyms) better than anchor 4, since the missing terms are among the most likely user utterances for this domain.	3 / 5
Distinctiveness Conflict Risk	"UI/UX design intelligence" carves out a fairly clear niche with domain-specific triggers (styles, palettes, font pairings, charts) that are unlikely to fire for unrelated skills. It is not a 5 because generic terms like "design" and "charts" could overlap with adjacent design/visualization skills.	4 / 5
	Total	12 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Draculabo/AntigravityManager
Path: .agent/skills/ui-ux-pro-max/SKILL.md
Commit: ccea788

Reviewed: 14 hours 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.