CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-review

Use when reviewing frontend code for design consistency, accessibility compliance, responsive behavior, and UI/UX best practices - before deployment or after design system changes.

Quality

82%

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

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.

A well-structured, highly actionable audit skill: concrete grep-based checks, clear severity levels, an explicit verification checklist, and a defined output format. The main weaknesses are minor — an unbound $TARGET variable, an unspecified 0-100 scoring methodology, some rule/checklist redundancy, and contrast verification lacking a concrete command.

Suggestions

Bind the target variable explicitly (e.g., note that $TARGET in the grep commands is the resolved $ARGUMENTS path) so every command is executable as written.

Define how the per-category 0-100 scores and the overall verdict thresholds (PASS / PASS WITH NOTES / NEEDS WORK / FAIL) are computed, so Step 6 is reproducible.

Add a concrete verification method for the 4.5:1 contrast criterion (e.g., a named tool or calculation step), since it is the one accessibility check with no executable command.

DimensionReasoningScore

Conciseness

The body is dense and operational — checklist tables, executable grep commands, and a severity taxonomy — with no explanation of concepts Claude already knows (no 'what is WCAG/Tailwind' padding). Minor trimmable redundancy keeps it below anchor 5: the Rules section repeats Verification Protocol items (file:line evidence, token-first checking), and the Anti-Rationalization table is extra framing beyond the core audit procedure.

4 / 5

Actionability

Concrete, executable grep commands cover the common cases (hardcoded colors, missing alt text, unlabelled inputs, fixed widths, missing responsive images) and the output template is copy-paste ready. Minor gaps hold it at anchor 4 rather than 5: '$TARGET' is used in commands but never bound to '$ARGUMENTS', 'Calculate scores per category (0-100)' specifies no scoring method, and the 4.5:1 contrast check lists no verification command or tool.

4 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with an explicit Verification Protocol checklist ('Before claiming the review is complete:') and a false-positive re-check (Rule 7), which fits anchor 4's 'clear sequence with most checkpoints present'. It falls short of anchor 5 because the per-category scoring step is undefined and there are no error-recovery/feedback loops for ambiguous findings.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~200-line body is well-sectioned with headers, tables, and code blocks so all inline content is scannable and appropriately placed — matching anchor 4's 'good structure; most content is appropriately placed'. It does not reach 5 because it exceeds the under-50-line simple-skill case, and the accessibility/UX checklists could arguably be split into one-level-deep reference files to keep SKILL.md leaner.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong description that explicitly covers both what the skill does and when to use it, with concrete timing triggers and natural keyword phrases. Its main limitations are a single generic verb ('reviewing'), a few missing common trigger synonyms (design audit, WCAG, a11y), and slight overlap with general code-review skills.

DimensionReasoningScore

Specificity

The description names four concrete review dimensions ("design consistency, accessibility compliance, responsive behavior, and UI/UX best practices") within the frontend-code domain, giving broad coverage with only minor gaps (e.g., the findings/severity output is unstated). It is more specific than anchor 3's '1-2 concrete actions' coverage, but the single verb 'reviewing' keeps it below anchor 5's multiple distinct concrete actions.

4 / 5

Completeness

An explicit "Use when..." clause is present (satisfying the cap guideline), the 'what' is concrete (reviewing frontend code for four named concerns), and the 'when' gives concrete timing triggers ("before deployment or after design system changes"). Both what and when are clearly and explicitly answered with concrete trigger phrases, matching anchor 5 rather than anchor 4 where the 'when' would need to be more explicit or specific.

5 / 5

Trigger Term Quality

Natural phrases users would say appear directly: "reviewing frontend code", "design consistency", "accessibility compliance", "responsive behavior", "before deployment", "after design system changes". Coverage is good but misses common variations like "design audit", "WCAG", "a11y", or "UI review", so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The design/accessibility/UI-audit niche is clearly distinct from most skills, but "reviewing frontend code" carries minor overlap risk with general code-review skills (the body itself defers to '/codereview'). This matches anchor 4's 'mostly distinct; minor overlap risk with closely related skills' rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/specialist-agent

Path

skills/design-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.