CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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: 80 searchable styles (51 active), 192 product palettes and reasoning profiles, 74 font pairings, 120 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

Quality

87%

Does it follow best practices?

Impact

93%

1 of 3 eval scenarios. Add 2 more for a full score.

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.

Highly actionable, clearly sequenced, and well-structured progressive disclosure with verified bundle references. The main cost is token efficiency: several sections repeat guidance or stats that appear elsewhere in the skill.

Suggestions

Remove the opening line that restates the frontmatter's data-catalog statistics (80 styles, 192 palettes, etc.) verbatim, or keep only one of the two.

Merge the 'If a search returns 0 results' section into the Query Contract's retry guidance (or vice versa) and drop the overlapping bullets in 'Tips for Better Results' — the retry-once rule and 2–5-term guidance are currently stated three times.

State the full script path once (e.g. define it as a single command template or variable) instead of repeating the entire ${CLAUDE_PLUGIN_ROOT}/... invocation in every code block.

DimensionReasoningScore

Conciseness

The body is mostly operational, but it duplicates the frontmatter's data-catalog statistics verbatim in the opening line, states the retry-once/empty-result protocol twice (Query Contract and the 'If a search returns 0 results' section), restates query-contract bullets in 'Tips for Better Results', and repeats the full script path in every code block. This is more than minor trimming, matching 'mostly efficient but could be tightened' rather than the efficient 4 anchor.

3 / 5

Actionability

Fully executable throughout: exact copy-paste commands with all flags (--design-system, --domain, --stack, --rtl, --persist, --output-dir, the three design dials), a per-domain example-query table, and a worked end-to-end example workflow for a detected Next.js project.

5 / 5

Workflow Clarity

Steps 1→4 are explicitly sequenced with a required gate for new pages (Step 2 REQUIRED), result verification before applying ('Verify the returned domain/category, top result identity, and fit'), an explicit retry-then-fallback feedback loop for empty or off-topic results, and safe-persistence checks (read existing MASTER.md, never --force without user authorization).

5 / 5

Progressive Disclosure

A clear overview with well-signaled one-level-deep references: references/quick-reference.md and references/pro-rules.md (both verified present) are each introduced with their purpose and an on-demand loading instruction, the priority table stays as a compact overview, and the Tips table links to specific quick-reference sections (§5–§9).

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 with an explicit 'should be used when' trigger clause, broad natural keyword coverage, and a well-scoped UI/UX niche. The only weaknesses are actions stated at a fairly abstract altitude and a few missing user-side synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ("designing, building, reviewing, or fixing interfaces") and enumerates scope areas (pages, components, design systems, accessibility, typography, color, charts) plus a searchable-data capability inventory. It stays at the "interfaces" altitude rather than detailing each action, so it matches 'several specific actions; minor gaps' rather than the comprehensive 5 anchor.

4 / 5

Completeness

Both halves are explicit: the what ("UI/UX design intelligence for web, mobile, and desktop" backed by a described searchable data catalog) and an explicit when clause ("This skill should be used when designing, building, reviewing, or fixing interfaces, including...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered ("designing, building, reviewing, or fixing", "pages, components", "accessibility", "responsive layout", "typography", "color", "charts"), but common synonyms like "frontend", "mockup", "wireframe", or "CSS" are absent, matching 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

A clear UI/UX design niche with distinct triggers that would not fire for backend or data-processing skills; only minor overlap risk with dedicated charting/dataviz skills via the "charts" and "stack-specific UI implementation" terms, matching 'mostly distinct; minor overlap risk'.

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

Path

.claude/skills/ui-ux-pro-max/SKILL.md

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.