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 Open Design.

48

Quality

53%

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

57%

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-organized, honest catalog-only entry that correctly signals the upstream workflow is not locally available and routes users to install it. Its main weaknesses are repetition of the not-bundled caveat and only partial actionability since the real workflow lives upstream.

Suggestions

Consolidate the 'catalog-only / not bundled' messaging into one section to reduce repetition across 'What it does', 'Current Open Design scope', and 'How to use'.

Provide a single concrete install snippet (e.g., a clone/copy command with the expected target skills-directory path) instead of only `open <url>` plus a prose instruction.

Make the fallback flow explicit as numbered steps (check for upstream files -> if missing, explain catalog-only -> offer Open Design default guidance) to sharpen the conditional sequence.

DimensionReasoningScore

Conciseness

The body is reasonably lean and does not explain concepts Claude already knows, but the 'catalog-only / not bundled' caveat is restated across 'What it does', 'Current Open Design scope', and 'How to use' and could be tightened. It is not level 3 due to that repetition, and not level 1 because it is not padded with background.

2 / 3

Actionability

It gives one concrete command (`open https://github.com/...`) and instructs installing the upstream bundle and invoking by name/trigger, but the real workflow is unavailable locally so guidance is incomplete and lacks executable detail. It is not level 3 because nothing is copy-paste ready, and not level 1 because some concrete direction exists.

2 / 3

Workflow Clarity

A loose sequence is present (install upstream -> invoke by name/trigger -> if absent, explain and offer default guidance) with a fallback branch, but the steps are informal and lack explicit checkpoints. Not level 3 because sequencing is not crisp; not level 1 because the flow is followable.

2 / 3

Progressive Disclosure

The skill is under 50 lines, has no bundle files requiring navigation, and is organized into clear sections (What it does, Current scope, Source, How to use). Per the rubric's simple-skills note, this earns a 3 with just well-organized sections.

3 / 3

Total

9

/

12

Passed

Description

50%

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 clearly conveys this is a catalog-only metadata entry rather than a functional skill, but it lacks concrete actions, natural trigger phrasing, and explicit 'use when' guidance. It reads as scope/existence metadata rather than a capability description.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., UI/UX patterns, usability heuristics) so the description answers when to invoke it.

State at least one concrete action the entry performs locally (e.g., 'Surfaces the upstream UI/UX Pro Max workflow for discovery during planning') rather than only describing what is absent.

Replace the generic 'design patterns' / 'usability' triggers with more distinctive phrasing tied to the named skill to reduce conflict risk.

DimensionReasoningScore

Specificity

The description names the domain and concrete content ('templates, data, and search workflow') but describes no actions the skill performs, since it is explicitly catalog-only. It is not level 1 because it is not purely vague, and not level 3 because no specific actions are listed.

2 / 3

Completeness

It states what the entry is ('Catalog-only UI/UX Pro Max entry... not bundled in Open Design') but provides no 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2.

2 / 3

Trigger Term Quality

It contains 'UI/UX Pro Max', 'templates', and 'search workflow', which are relevant but miss common natural variations a user would actually say. It is below 3 because coverage of natural trigger terms is thin, and above 1 because some relevant keywords are present.

2 / 3

Distinctiveness Conflict Risk

It targets a named niche ('ui-ux-pro-max') but its associated triggers ('design patterns', 'usability') are generic and could overlap with similar skills. Not level 3 because of conflict risk, not level 1 because the niche is named.

2 / 3

Total

8

/

12

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.