Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/ux-evaluator
This skill should be used when evaluating UI components against UX best practices.
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 8 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Could you audit the action area at the bottom of our user registration form? We currently have the main submit button full-width at the top of the action stack with an outline style, and the clear form button positioned on the right side below it. Please record the baseline specs, evaluate position, visual weight, and spacing in a structured comparison table, render a final verdict, and provide prioritized action items if adjustments are needed.
| Checked | Without skill | With skill |
|---|---|---|
| The response includes an Analysis section. | Passed | Passed |
| The response recommends giving the primary submit button a filled background style. | Passed | Passed |
| The response includes priority rankings in the recommendations table. | Missed | Passed |
The instructions your model reads when the skill loads.
Systematically evaluate UI components against established UX principles using a 3-dimension framework. Transform subjective design feedback into actionable, evidence-based recommendations by comparing against industry conventions and authoritative sources.
Core Value: Prevents subjective design debates by grounding decisions in documented best practices.
Triggers:
Do NOT use for:
For ANY UI component, evaluate these three dimensions:
| Dimension | What to Analyze | Key Questions |
|---|---|---|
| 1. Position | Where is it located relative to other elements? | Does position follow conventions? Is it discoverable? |
| 2. Visual Weight | How prominent is it visually? | Does it compete with primary actions? Is hierarchy clear? |
| 3. Spacing | What's the gap from adjacent elements? | Is there adequate separation? Is spacing consistent? |
Step 1: GATHER CONTEXT
├── What component is being evaluated?
├── What user feedback or concern triggered this?
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.