CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-ux-pro-max

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/04-develop/01-ui-skills-dot-com/ui-ux-pro-max/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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-organized with a clear 4-step workflow, sensible defaults, and genuinely dense reference tables, but it is undermined by a bundle that omits every file the workflow depends on — the search script and its data are absent, making all commands non-executable. Significant duplication (dual How-to-Use sections, verbatim-repeated example commands, overlapping rule tables) further inflates the token cost.

Suggestions

Ship the actual bundle: include scripts/search.py and its data files (e.g., ui-reasoning.csv) under the skill directory, and fix the path so commands run relative to the skill's location rather than the assumed 'skills/ui-ux-pro-max/...' prefix.

Move the Quick Reference rule lists, Common Rules tables, and Pre-Delivery Checklist into a references/ file (e.g., references/rules.md) and keep SKILL.md as a concise overview pointing to it, removing the duplicated How-to-Use sections and the verbatim-repeated Example Workflow commands.

Delete the OS-specific Python installation instructions — verifying Python is fine, but brew/apt/winget install steps explain something Claude already knows and waste context.

DimensionReasoningScore

Conciseness

The core reference tables are dense and valuable ("Minimum 44x44px touch targets", "4.5:1 ratio", "z-index scale (10, 20, 30, 50)", "150-300ms"), but there are several padded sections: OS-specific Python installation instructions Claude already knows (brew/apt/winget), a duplicated "How to Use" vs. "How to Use This Skill" pair, an "Example Workflow" that re-runs the exact commands from Steps 2-4 verbatim, and "Common Rules" tables that repeat rules already in the Quick Reference (no-emoji-icons, contrast values). Mostly efficient but could be tightened — fits anchor 3, not 4 due to the volume of duplication.

3 / 5

Actionability

Concrete, specific commands with flags and examples throughout ("python3 skills/ui-ux-pro-max/scripts/search.py \"<query>\" --design-system --persist -p \"Project Name\" --page \"dashboard\""), but every command invokes scripts/search.py, which does not exist in the bundle (no scripts/ directory), so nothing is executable as shipped — a missing key component that fits anchor 3's 'concrete guidance but incomplete', and rules out 4's 'mostly executable'.

3 / 5

Workflow Clarity

A clear 4-step sequence (analyze requirements -> generate design system -> supplement with domain searches -> stack guidelines) with defaults ("default to html-tailwind"), a worked example, and a Pre-Delivery Checklist serving as a validation checkpoint. Not 5 because there are no error-recovery feedback loops beyond the tip "If first search doesn't match, try different keywords", and the workflow depends on commands that fail against the missing script.

4 / 5

Progressive Disclosure

The bundle contains no references/, scripts/, or assets/ files, yet the body repeatedly references "skills/ui-ux-pro-max/scripts/search.py" and "ui-reasoning.csv" — broken, absent references — while ~150 lines of reference material (Quick Reference rule lists, Common Rules tables, checklists) that clearly belongs in separate files are inlined into a 385-line SKILL.md. This matches anchor 2 ('content that clearly belongs in separate files is inlined; or references are buried/broken'); it is not 3 because the cross-file structure the skill depends on does not exist at all.

2 / 5

Total

12

/

20

Passed

Description

70%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 keyword-dense catalog description with excellent natural trigger terms and a concrete asset inventory, but no explicit 'Use when...' invocation clause and an over-broad action list that inflates conflict risk. The counts also contradict the body (21 palettes/50 font pairings/20 charts in the description vs. 97/57/25 in the body).

Suggestions

Add an explicit trigger clause, e.g. "Use when designing or reviewing UI for websites and apps, choosing styles/palettes/typography, or when the user mentions landing pages, dashboards, or specific styles like glassmorphism or bento grid."

Trim the generic action list (plan, build, create, fix, improve, optimize, enhance, refactor) to the skill's actual capabilities (generate design systems, recommend styles/palettes/font pairings, review UI code) to reduce overlap with general web-dev skills.

Reconcile the asset counts between description and body (e.g., 21 vs. 97 palettes) so the description accurately reflects the bundle.

DimensionReasoningScore

Specificity

Quotes a concrete catalog ("50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui)" and "Integrations: shadcn/ui MCP for component search and examples"), which lists several specific capabilities. It is not a 5 because the action list ("plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor") is generic rather than concrete, and not a 3 because more than 1-2 concrete capabilities are explicitly enumerated.

4 / 5

Completeness

The "what" is clear ("UI/UX design intelligence" with an enumerated asset catalog), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "Actions:", "Projects:", and "Elements:" lists are catalogs, not invocation guidance. Per the judging guideline, a missing 'Use when' clause caps completeness at 3; it is above 2 because the 'what' is explicit and detailed, and below 4 because 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Comprehensive natural terms with synonyms and file extensions: "website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte" plus "glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive" and "color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient". Matches the anchor for comprehensive coverage including file extensions.

5 / 5

Distinctiveness Conflict Risk

The UI/UX design niche is somewhat specific ("glassmorphism", "font pairing", "shadcn/ui MCP"), but the extremely broad action and project lists ("build, create, fix, improve, optimize, enhance, refactor... website, landing page, dashboard... .html, .tsx") would trigger on nearly any frontend task and overlaps with chart/dataviz and general web-dev skills. Not 2 because it is clearly anchored to a design-intelligence domain rather than being generic; not 4 because the claimed scope covers most frontend work.

3 / 5

Total

15

/

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

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/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.