CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-ux-pro-max

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

80

1.86x
Quality

84%

Does it follow best practices?

Impact

80%

1.86x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually actionable skill body: verified copy-paste commands, a priority-ordered decision table, explicit zero-result handling with fallback labeling, and destructive-write safeguards, with clean one-level-deep progressive disclosure into two real reference files. The one real weakness is redundancy — the query-discipline rules are stated three times across Query Contract, the 0-results section, and Tips.

Suggestions

Delete the opening 'Searchable local UI/UX guidance: 79 searchable styles (50 active), 192 product palettes...' line — it duplicates the frontmatter description verbatim and adds nothing the priority table and domain tables don't already convey.

Merge the 'If a search returns 0 results' section into the Query Contract's existing retry rules (they repeat each other), keeping only the unique parts: the explicit built-in-defaults fallback and the 'never present a 0-result search as if it returned data' rule.

Cut the first three bullets of 'Tips for Better Results' ('one dominant intent and 2–5 meaningful terms', 'Retry once', '--design-system vs --domain') — all three restate the Query Contract — and keep only the troubleshooting table, which adds genuinely new pointers.

DimensionReasoningScore

Conciseness

The body is dense with commands and tables and explains no basic concepts, but ~20 lines are redundant: the opening inventory line repeats the frontmatter description verbatim, the "If a search returns 0 results" section restates Query Contract's retry/fallback rules, and the first three Tips bullets duplicate "one dominant intent, 2–5 meaningful terms" and "retry once" guidance already given. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than 4's 'minor instances', since three separate sections repeat the same query discipline.

3 / 5

Actionability

Fully executable throughout: exact copy-paste commands with the absolute "${CLAUDE_PLUGIN_ROOT}/.claude/skills/ui-ux-pro-max/scripts/search.py" path, per-domain example queries, a full stack list, the dial table, and a worked example workflow. Every documented flag (--design-system, --persist, --page, --force, --variance/--motion/--density, -f, --json) was verified against scripts/search.py and matches.

5 / 5

Workflow Clarity

Steps 1→4 are clearly sequenced with explicit validation and feedback loops: retry-once with narrower rewrite on empty/off-topic results, then fall back to the priority table while explicitly labeling output as built-in defaults, and "never present a 0-result search as if it returned data". Destructive operations are guarded (existing MASTER.md is skipped unless --force; read it before --force; never force without user authorization), and checklists exist (priority table, Pre-Delivery Checklist reference). Not 4 because checkpoints, error-recovery loops, and checklists are all explicit rather than merely 'mostly present'.

5 / 5

Progressive Disclosure

Scored against the actual bundle: the body is an overview whose bulk data (119 UX guidelines, palettes, icons, presets) is reachable via the search tool rather than inlined, and only two references exist (references/quick-reference.md, references/pro-rules.md) — both real files, one level deep, clearly signaled with on-demand read instructions and specific, verified section pointers (§3–§9, named tokens like color-dark-mode and spring-physics all confirmed present).

5 / 5

Total

18

/

20

Passed

Description

83%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 description: explicit and specific 'should be used when' trigger guidance, concrete enumerated scope, and third-person voice. Main gaps are a few missing natural synonyms (frontend, mockups, CSS) and an abstract 'design intelligence' framing that keeps specificity just short of comprehensive.

DimensionReasoningScore

Specificity

Concrete action verbs ("designing, building, reviewing, or fixing interfaces") plus a specific data inventory ("79 searchable styles", "192 product palettes", "74 font pairings") give several specific capabilities. Not 5 because "UI/UX design intelligence" frames capabilities somewhat abstractly and the verbs are broad rather than fine-grained; clearly above 3's '1-2 concrete actions' since multiple actions and concrete scope are enumerated.

4 / 5

Completeness

Explicitly answers both: what — "UI/UX design intelligence for web, mobile, and desktop" with an itemized data inventory; and when — "This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems..." with concrete trigger activities. Not 4 because the 'when' clause is specific and enumerated, not merely present-but-vague.

5 / 5

Trigger Term Quality

Natural phrases a user would say appear throughout: "interfaces", "pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts". Not 5 because common synonyms and variants are missing (e.g., "frontend", "mockups", "wireframes", "CSS", "mobile app"); well above 3 since keyword coverage is broad and natural rather than merely relevant.

4 / 5

Distinctiveness Conflict Risk

A clear UI/UX design niche with trigger vocabulary (typography, GSAP presets, font pairings) that most skills would not claim. Not 5 because its deliberate breadth across web/mobile/desktop and charts creates minor overlap risk with chart-specific or stack-specific skills; well above 3 since the trigger set is distinctly design-oriented.

4 / 5

Total

17

/

20

Passed

Validation

100%

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
nextlevelbuilder/ui-ux-pro-max-skill
Reviewed

Table of Contents

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.