CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-ux-pro-max

UI/UX design intelligence with searchable database

51

Quality

64%

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 ./app/skills/ui-ux-pro-max/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a well-structured, highly actionable guide with clear workflows and concrete commands. Its main weaknesses are the missing CSV data files referenced by the scripts, some over-explained prerequisites, and inline content that would benefit from being split into reference files.

Suggestions

Include the referenced data files (ui-reasoning.csv, styles.csv, colors.csv, etc.) in the bundle or document where they are generated, so the cited commands actually run.

Move the 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' into a separate reference file (e.g. CHECKLIST.md) and link to it, keeping SKILL.md a lean overview.

Remove the OS-specific Python installation prerequisites; Claude already knows how to install Python, so a single version check suffices.

DimensionReasoningScore

Conciseness

Most of the body is efficient and concrete, but the Prerequisites section with OS-specific Python install commands (brew/apt/winget) explains something Claude already knows and could be trimmed.

3 / 5

Actionability

It provides concrete, copy-pasteable search.py commands with flags, domain/stack tables, and worked examples; minor gaps are placeholder queries and the absence of the referenced CSV data files in the bundle.

4 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced with REQUIRED flags and a Pre-Delivery Checklist acting as a validation gate, though explicit error-recovery feedback loops for failed searches are not detailed.

4 / 5

Progressive Disclosure

Referenced scripts are real and one level deep, but the data files cited (ui-reasoning.csv and the per-domain CSVs) are missing from the bundle, and large inline reference-style content (Common Rules, Pre-Delivery Checklist) could live in separate files.

3 / 5

Total

14

/

20

Passed

Description

48%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 identifies a clear niche but is thin: it states a domain and a mechanism without concrete actions or an explicit use-when clause. It reads more like a tagline than a trigger-rich capability statement.

Suggestions

Add concrete actions, e.g. 'Generates design systems, recommends color palettes, font pairings, and chart types from a searchable database.'

Append an explicit trigger clause, e.g. 'Use when designing or building UI/UX for web or mobile apps, or when the user mentions color, typography, landing pages, or dashboards.'

Include natural synonyms users actually say ('interface', 'user experience', 'design system') to improve trigger matching.

DimensionReasoningScore

Specificity

It names the domain ('UI/UX design intelligence') but the only capability cited ('searchable database') describes a mechanism rather than a concrete user-facing action like generating design systems or recommending palettes.

2 / 5

Completeness

It conveys a recognizable 'what' (UI/UX design tooling) but provides no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'UI/UX design' is a natural phrase users say, but the description misses common variations/synonyms such as 'interface', 'user experience', 'landing page', or 'color palette'.

3 / 5

Distinctiveness Conflict Risk

The UI/UX design niche is mostly distinct with clear triggers, though it carries minor overlap risk with general frontend/design skills.

4 / 5

Total

12

/

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
ZHangZHengEric/Sage
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.