CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-ux-pro-max

UI/UX design intelligence with searchable database

46

Quality

48%

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 ./.opencode/skills/ui-ux-pro-max/SKILL.md

The canonical home for this skill is ui-ux-pro-max in BiFangKNT/mtga

SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured and highly actionable, with executable commands, decision tables, a gated workflow, and a worked example backed by real bundled scripts. Its main weaknesses are verbosity from duplicated and overlapping sections, and a small stack-list mismatch versus the actual CLI.

Suggestions

Consolidate the "Common Rules for Professional UI" tables and the "Pre-Delivery Checklist" into a single reference file, keeping only a short pointer in SKILL.md.

Remove the standalone "Example Workflow" section or fold it into Step 2 as a single inline example to avoid duplicating the workflow already shown above.

Reconcile the stack list (line 118) with the script's actual --stack choices, or note which stacks are supported for design-system vs. stack-guideline searches.

DimensionReasoningScore

Conciseness

Command examples and tables are dense and efficient, but the per-OS Python install prerequisites, a duplicated full Example Workflow, and the overlapping "Common Rules" + "Pre-Delivery Checklist" sections add padding beyond minor trimming.

3 / 5

Actionability

Concrete executable commands with real verified flags, a need-to-domain decision table, and a worked end-to-end example; minor gap is the stack list (10 stacks) mismatching the script's actual --stack choices (html-tailwind, react, nextjs).

4 / 5

Workflow Clarity

A clear 4-step sequence with an explicit REQUIRED gate and a worked example, plus well-explained hierarchical retrieval; the only gap is the lack of an explicit validate/refine-and-retry checkpoint within the steps.

4 / 5

Progressive Disclosure

SKILL.md acts as an overview with heavy data pushed to CSVs accessed via scripts, real one-level-deep script references, and clear section navigation; minor gaps are that the CSV data layer is not explicitly signaled and two large rules/checklist sections are inlined.

4 / 5

Total

15

/

20

Passed

Description

28%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.

The description is concise but too vague: it names the domain without listing concrete actions, omits any use-when trigger guidance, and offers only one natural user keyword. It is recognizable as a UI/UX niche yet lacks the explicit triggers that would distinguish it.

Suggestions

Add concrete actions, e.g. "Generates design systems with styles, color palettes, font pairings, and chart recommendations..." instead of "design intelligence".

Append a "Use when..." clause with natural triggers, e.g. "Use when the user asks to design, build, review, or improve a UI; choose colors, fonts, or layouts; or build a landing page."

Include synonyms and concrete deliverables users mention (landing page, dashboard, dark mode, accessibility, brand styling) to raise trigger-term coverage.

DimensionReasoningScore

Specificity

"UI/UX design intelligence with searchable database" names the domain but offers only abstract capability nouns ("design intelligence", "searchable database") rather than concrete actions like generate, recommend, or extract.

2 / 5

Completeness

A vague "what" is present but there is no "when"/"Use when..." clause at all, capping completeness low and matching the anchor with a vague what and no when.

2 / 5

Trigger Term Quality

Only "UI/UX design" is a term a user might say; "searchable database" is an implementation descriptor, and natural request phrases like "design a landing page", "pick colors", or "choose fonts" are absent.

2 / 5

Distinctiveness Conflict Risk

UI/UX design is a recognizable niche, but without explicit trigger phrases it could still overlap with generic frontend or design skills.

3 / 5

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
trackdubllc/Babel-Player-Alpha
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.