ui-ux-pro-max

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

Quality

58%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with copy-paste commands, clear tables, and a well-sequenced workflow plus delivery checklist. Its main weaknesses are token padding from basic-knowledge sections and a monolithic structure that inlines reference material instead of splitting it into signaled separate files.

Suggestions

Remove or trim the multi-OS Python installation prerequisites and the 'Common Rules for Professional UI' tables, since these restate knowledge Claude already has.

Move the 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' into a separate referenced file (e.g. checklists.md) linked one level deep from the overview.

Ensure the bundle ships the data/ CSVs (ui-reasoning.csv, styles.csv, etc.) the scripts reference, or document that they are generated/loaded elsewhere.

Dimension	Reasoning	Score
Conciseness	The command and domain/stack tables are efficient reference material, but the Python-install prerequisites for three OSes and the 'Common Rules for Professional UI' (cursor-pointer, hover, contrast basics) restate concepts Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	Commands like 'python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"' are specific, copy-paste ready, and paired with concrete example queries and full domain/stack tables, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clear 4-step sequence (Analyze -> Generate Design System -> Supplement -> Stack Guidelines, plus 2b persist) is paired with a worked example and an explicit Pre-Delivery Checklist acting as a verification checkpoint before delivery; the task is non-destructive so no feedback-loop cap applies.	3 / 3
Progressive Disclosure	Sections are well-organized and the searchable-database concept keeps bulk data out of context, but the SKILL.md still inlines large reference blocks (Common Rules tables, Pre-Delivery Checklist) that could be separate files, has no clearly-signaled one-level-deep .md references, and the data/ CSVs the scripts depend on are absent from the actual bundle.	2 / 3
	Total	10 / 12 Passed

Description

40%

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 identifies the UI/UX design niche and the searchable-database mechanism, but it is vague about concrete capabilities and entirely lacks explicit 'when to use' trigger guidance. It reads more as a tagline than an actionable, distinctive skill description.

Suggestions

Add concrete actions, e.g. 'Generate design systems, recommend color palettes, font pairings, and UX guidelines for web and mobile apps'.

Append an explicit trigger clause such as 'Use when the user asks to design, build, review, or improve a UI/UX for web or mobile applications'.

Include natural keyword variations users would say (landing page, dashboard, color palette, typography) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'UI/UX design intelligence with searchable database' names the domain but lists no concrete actions (e.g. 'generate design systems', 'search color palettes'), matching the vague/abstract anchor rather than the 'names domain and some actions' level.	1 / 3
Completeness	It states a weak 'what' (design intelligence + searchable database) but offers no 'when'/'Use when' trigger guidance; the missing explicit trigger clause caps this at 2, and it does not reach the both-what-and-when anchor.	2 / 3
Trigger Term Quality	'UI/UX design' is a natural term a user would say, but the description misses common variations like 'landing page', 'dashboard', 'color palette', or 'fonts', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The UI/UX design niche is somewhat specific and unlikely to conflict with non-design skills, but the thin, generic phrasing ('design intelligence') keeps it from the clear-distinct-triggers anchor.	2 / 3
	Total	7 / 12 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: de8d68d

Reviewed: about 12 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.