ui-ux-pro-max

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

Quality

65%

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

71%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 highly actionable with concrete commands, a clear four-step workflow, and a useful pre-delivery checklist. Its weaknesses are an over-explanatory Python-install prerequisite section, a missing in-workflow validation loop, and a missing data directory that the scripts depend on.

Suggestions

Trim or remove the OS-by-OS Python installation instructions; assume Claude can install Python if missing, and reduce this to a single version check.

Add an explicit validation/feedback step within the generation workflow (e.g. verify the generated design-system output covers the requested product type before proceeding) rather than relying solely on the post-hoc checklist.

Ship the referenced `data/` CSVs (including `ui-reasoning.csv`) in the bundle or document where they live, since `core.py` resolves them relative to the script and they are required for the commands to run.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized command examples, but the Prerequisites section walks through installing Python on macOS/Ubuntu/Windows — a concept Claude already knows — which is unnecessary padding, matching the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready bash commands with concrete flags and a fully worked example query (e.g. `python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"`), covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	Steps 1-4 are clearly sequenced and the Pre-Delivery Checklist supplies a validation checkpoint, but the design-generation steps themselves lack an explicit validate-then-retry feedback loop, fitting the score-4 anchor of a clear sequence with most checkpoints present and minor validation gaps.	4 / 5
Progressive Disclosure	Sections and tables are organized, but all reference content (domain/stack tables, common-rules tables, checklist) is inlined in a single ~310-line SKILL.md with no separate reference docs, and the CSV data files referenced by the scripts (e.g. `ui-reasoning.csv`, the `data/` directory) are absent from the bundle, matching the score-3 anchor of some structure with content that should be separate kept inline.	3 / 5
	Total	15 / 20 Passed

Description

58%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 concise and packs in concrete catalog figures, but it is noun-heavy with no action verbs and entirely lacks a 'when to use' trigger clause, capping completeness. It is distinct and uses natural trigger terms but reads more like a feature list than actionable guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to design, build, or review UI/UX for web or mobile apps.'

Lead with a concrete action verb in third person (e.g. 'Generates UI/UX design systems...') instead of the static noun phrase 'UI/UX design intelligence.'

Reconcile the figures with the body (description says 50 styles/9 stacks while the body claims 67 styles/13 stacks) so the description is not self-contradictory.

Dimension	Reasoning	Score
Specificity	The description names the domain ("UI/UX design intelligence") and enumerates specific catalog contents ("50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks"), but lists categories rather than concrete actions, matching the score-3 anchor of naming a domain with limited action specificity.	3 / 5
Completeness	It clearly states what the skill is ("UI/UX design intelligence" with a concrete catalog) but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3 with a clear 'what' and missing 'when'.	3 / 5
Trigger Term Quality	Terms like "UI/UX", "design", "styles", "palettes", "font pairings", "charts", and "stacks" are natural keywords users would say, giving good coverage with only minor variations (e.g., "themes", "color schemes") missing, fitting the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	The UI/UX design-intelligence niche with specific palette/chart/stack coverage is mostly distinct from other skills, with only minor overlap risk against generic design or styling skills, matching the score-4 anchor.	4 / 5
	Total	14 / 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: e29cfdc

Reviewed: 1 day 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.