CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-design

Use when users need visual direction, interface hierarchy, layout decisions, design specifications, or prototypes before implementing a Web or mini program UI.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./config/source/skills/ui-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 delivers a genuinely actionable design workflow with strong validation checkpoints and feedback loops, anchored by concrete thresholds and copy-paste audit commands. Its weaknesses are heavy systematic repetition of the same prohibitions across multiple sections and a monolithic structure with a dangling checklist.md reference and no realized bundle split.

Suggestions

State each prohibition (forbidden colors, forbidden fonts, emoji-as-icons, centered-layout rule) once in a single 'Hard constraints' section and have the trigger-word detector and self-audit reference it instead of re-listing the full rules — this would cut a large fraction of the body's tokens.

Merge the 'Activation Contract' and 'When to use this skill' sections, which currently duplicate overlapping trigger and exclusion lists ('Do NOT use for' appears in both with near-identical items).

Create the referenced checklist.md (or remove the link) and move the self-audit grep commands and anti-pattern code examples into it, so SKILL.md stays an overview with one-level-deep references that actually resolve.

DimensionReasoningScore

Conciseness

The same prohibitions are restated four to five times — forbidden colors appear in 'How to use' ("Never use forbidden colors (purple, violet, indigo..."), the design specification template, the trigger-word detector, the anti-patterns code block, and the color audit; the same is true for forbidden fonts and emoji-as-icons. Two separate activation sections ('Activation Contract' and 'When to use this skill') also duplicate each other's trigger/exclusion lists. This matches 'Noticeably verbose; several unnecessary explanations or padded sections' rather than 3, because the repetition is extensive and systematic.

2 / 5

Actionability

Mostly executable guidance: copy-paste grep audit commands, specific hex ranges for forbidden colors, concrete Tailwind/font-family code examples, a named 4-based spacing scale, and exact thresholds (contrast ≥4.5:1, tracking ≥-0.04em, 65–75ch measure). Not a 5 because sections like 'Creative Implementation Principles' and 'Backgrounds & Visual Details' remain directional ("Create atmosphere and depth", "make unexpected choices") rather than executable.

4 / 5

Workflow Clarity

The sequence is explicit and enforced: a MANDATORY design-specification output before any code, a six-step design process, and a self-audit checklist with concrete validation commands and feedback loops ("If found → VIOLATION → Choose alternative", "If any audit fails → Re-design with correct approach"). This matches the anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'.

5 / 5

Progressive Disclosure

The body has clear section headers and well-signaled references, but it is a ~395-line monolith with no bundle files: the referenced [UI Design Activation Checklist](checklist.md) does not exist in the bundle (dangling link), and content that clearly belongs in separate files (aesthetic options catalogue, anti-pattern code examples, audit commands) is inlined. This fits 'Some structure but could be better organized; references present but not clearly signaled' — structure exists, but the split is not actually realized.

3 / 5

Total

14

/

20

Passed

Description

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

A solid trigger-oriented description with an explicit 'Use when...' clause and good natural keywords for the UI-design niche. Its main weakness is that the skill's actions are only implied by a list of deliverable nouns rather than stated as concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ("Web or mini program UI") and lists deliverables ("visual direction, interface hierarchy, layout decisions, design specifications, or prototypes") but uses no concrete action verbs — it never states what the skill actually does (e.g., 'create prototypes', 'produce design specifications'). This matches 'names domain and 1-2 concrete actions, but not comprehensive' better than 4, which expects several specific actions.

3 / 5

Completeness

The 'when' is explicit and well-formed ("Use when users need... before implementing a Web or mini program UI"), and the 'what' is implied through the listed deliverables. This fits anchor 4 ('Has both what and when; one could be more explicit') — the what is the weaker half since no producing action is stated; a 5 requires both fully explicit with concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural phrases like "visual direction", "layout decisions", "design specifications", "prototypes", and "Web or mini program UI" give good keyword coverage, matching the anchor 'Good keyword coverage; a few natural terms missing'. Not a 5 because common user phrasings like "design", "styling", "look and feel", or "interface design" are absent.

4 / 5

Distinctiveness Conflict Risk

The scope is a clear niche — design decisions and specifications before implementation, specifically for Web or mini program UIs — with distinct triggers. It is 'mostly distinct; minor overlap risk' with closely related skills (e.g., a general web-development skill could also claim layout decisions), not a 5 with minimal conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 possibly missing (checklist.md)

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (assets/images/logo.png), 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/source/skills/ui-design/SKILL.md

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.