SKILLEMALL.ai
GitHub ↗ RU Sign in

CC ui-ux-pro-max

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

avelikiy/great_cto Agent Skills author: avelikiy MIT 34 files · 4 scripts body ≈ 11 202 tokens Open the sourcegithub.com↗ analyzed 11 d ago

UI/UX design intelligence for web and mobile.

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

ProcedureDesigntype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
95
Quality 40%
66
Run on models
none yet
Process rating
C
58/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
Execution cost w 6
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Exfiltration net-credential-use data/stacks/nuxtjs.csv:53
    Credential used in a network call (verify the destination is the intended service)
    52,Environment,Use runtimeConfig for env vars,Access environment variables safely,runtimeConfig in nuxt.config,process.env directly,"runtimeConfig: { apiSecret: '', public: { apiBase: '' } }",process.

Files scanned: 34. 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")
  • warning body-long SKILL.md body ≈ 11202 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 58/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Execution cost. Instruction body is 11202 tokens: crowds the task out of the window
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 60Steps. 277 steps, 8 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
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • 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 914: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 49 headings
  • +3Step-by-step instructions: 277 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)
  • +3All 3 scripts are documented
  • +1License stated

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