CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-review

Review UI code for design system compliance, accessibility, and best practices

Quality

69%

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 ./.agents/skills/ui-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a strong, disciplined review checklist: concrete thresholds, correct-vs-violation patterns, and a defined output format with essentially no filler. Its main weaknesses are dependence on external files that are not part of the bundle (CLAUDE.md font scale, VISUAL-CRAFT.md) and undefined pass/fail severity criteria.

DimensionReasoningScore

Conciseness

The body is a lean checklist with concrete violation examples (e.g. 'p-5=20px, gap-3.5=14px are violations') and almost no explanation of concepts Claude already knows; only minor trimming is needed (the generic 'Limitations' boilerplate and the 'When to Use' line that restates the description).

4 / 5

Actionability

Checklist items are highly concrete and checkable — specific tokens ('text-foreground', 'bg-brand'), exact thresholds (44x44px, 4.5:1, multiples of 6px) — but guidance depends on un-bundled external files ('see CLAUDE.md' for the 14-step font scale, 'VISUAL-CRAFT.md §C0'), leaving minor gaps versus fully executable guidance.

4 / 5

Workflow Clarity

The single-pass review workflow is unambiguous (review $ARGUMENTS file against the eight checklist sections, then emit Score/Issues/Fixes), and no destructive or batch operations require validation loops; the Pass/Needs Improvement/Fail criteria are undefined, a minor gap that keeps it below 5.

4 / 5

Progressive Disclosure

The body is well organized into eight clearly headed checklist categories plus output format, with no bundle files to nest; references to CLAUDE.md and VISUAL-CRAFT.md are external project files that are not clearly signaled, and the 14-step typography scale could live in a reference file — minor organization gaps consistent with anchor 4.

4 / 5

Total

16

/

20

Passed

Description

50%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 serviceable but mediocre: it states a clear single action and domain yet lacks any explicit 'when to use' trigger guidance, misses natural synonyms, and risks overlapping with the sibling review skills it coexists with. It reads like a terse title rather than an activation contract.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing or refactoring frontend component code, Tailwind/CSS markup, or when the user asks for a UI, design-system, or accessibility review.'

Include natural synonyms and concrete artifacts users would mention: 'a11y', 'frontend components', 'Tailwind classes', 'UI audit', 'design tokens'.

Sharpen distinctiveness by scoping the description to full-stack UI review (tokens + coherence + a11y + performance) so it clearly does not trigger for the narrower /ss-a11y, /ss-lint, or /ss-audit use cases.

DimensionReasoningScore

Specificity

The description names the domain ('UI code') and one action ('Review') across three focus areas ('design system compliance, accessibility, and best practices'), but 'best practices' is generic and no several specific actions are listed, matching anchor 3 rather than 4.

3 / 5

Completeness

The 'what' is clear (review UI code for design system compliance, accessibility, best practices) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'UI code', 'design system', and 'accessibility' are phrases users would naturally say, but common variations and synonyms (a11y, frontend, CSS/Tailwind, component review) are missing, which matches anchor 3 ('some relevant keywords but missing common variations').

3 / 5

Distinctiveness Conflict Risk

The UI design-review niche is somewhat specific, but 'accessibility' and 'best practices' overlap with the closely related skills the body itself defers to (/ss-a11y, /ss-lint, /ss-audit), fitting anchor 3 ('could still overlap with similar skills') better than anchor 4.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/ui-review/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.