SKILLEMALL.ai

BC 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.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 3 069 tokens Open the sourcegithub.com analyzed 2 d ago

UI/UX design intelligence.

As a process C 62/100 · Has gaps — weak spots: when it triggers, progress reporting

ProcedureDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
62/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Failures and branches w 10
55
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 62/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Steps. 74 steps, 5 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3069 tokens
  • 100Running it twice. Mutating operations check current state
  • low 12 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 806: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 74 items
  • +3Output format is stated explicitly
  • +4Has examples (12 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.