CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-ux-pro-max

Catalog-only UI/UX Pro Max entry. The full upstream templates, data, and search workflow are not bundled in OpenDesign.

54

Quality

61%

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

Quality

Content

71%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, honest catalog pointer that gives concrete install/invoke instructions and a clear fallback path. Its main weakness is redundant restating of the "not bundled" message across sections, which adds tokens without new information.

Suggestions

Collapse the repeated "not bundled / not available" statements into a single scope section so the message is stated once.

Avoid restating the frontmatter description verbatim in "What it does"; let the section add information instead.

Optionally give one concrete install hint (e.g. the expected upstream skill directory name) to close the gap in the otherwise vague install step.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of generic concept explanations, but the "not bundled / not available" message is repeated across "What it does", "Current OpenDesign scope", and "How to use", and the description is restated verbatim in "What it does".

3 / 5

Actionability

It provides a concrete command (`open https://github.com/nextlevelbuilder/ui-ux-pro-max-skill`), an invoke-by-name instruction, and a clear fallback procedure, with only minor gaps in the upstream-install step.

4 / 5

Workflow Clarity

The "How to use" section sequences install → inspect README → invoke by name/trigger, with an explicit conditional fallback when upstream files are absent; no destructive or batch operation is involved so the validation cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no local bundle files (references/, scripts/, assets/ are empty) and is organized into clear, well-signaled sections pointing one level deep to the upstream repo, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

52%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 honestly conveys the catalog-only nature of the entry and lists reasonable triggers, but it lacks concrete capability actions and any explicit use-when guidance. The broad "design patterns" trigger introduces overlap risk with unrelated engineering skills.

Suggestions

Add an explicit "Use when..." clause naming concrete UI/UX scenarios so the when-to-use is stated, not implied.

Replace or qualify the "design patterns" trigger with something UI-specific (e.g. "ui design patterns") to reduce conflict with software design-pattern skills.

Describe at least one concrete capability of the upstream skill (e.g. "searches a UI/UX pattern library") instead of only stating what is absent.

DimensionReasoningScore

Specificity

The description states it is a "Catalog-only UI/UX Pro Max entry" and that the full workflow is "not bundled in OpenDesign" — it names the domain but describes no concrete skill actions, only the catalog status.

2 / 5

Completeness

It gives a clear "what" (a catalog-only entry whose full workflow is not bundled) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Frontmatter triggers include "ui ux patterns", "ux heuristics", and "usability", which are natural terms users would say, though a few synonyms (e.g. "user experience", "UI/UX design") are missing.

4 / 5

Distinctiveness Conflict Risk

The "ui-ux-pro-max" niche is fairly specific, but the trigger "design patterns" is broad and overlaps with software design-pattern skills, creating moderate conflict risk.

3 / 5

Total

12

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
nexu-io/open-design
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.