CtrlK
BlogDocsLog inGet started
Tessl Logo

web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

66

Quality

79%

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 ./packages/skills-catalog/skills/(design)/web-design-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured with good progressive disclosure and a clear read-only workflow, but it is held back by redundant step repetition and by deferring essentially all actionable detail to the referenced guideline file rather than carrying the key rules inline.

Suggestions

Collapse the 'How It Works' and 'Usage' sections into a single sequenced workflow to remove the repeated four-step list and the triplicate guideline-path reference.

Inline the output format and a few of the highest-value rules directly in SKILL.md so the skill is actionable without first opening references/guideline.md.

Add an explicit verification checkpoint (e.g., 'confirm every guideline category was checked before reporting findings') to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept over-explanation, but the 'How It Works' and 'Usage' sections repeat nearly the same four-step process and the guideline reference path is stated three times (inline, code block, and again in Usage), which is noticeable padding.

3 / 5

Actionability

Steps are concrete and sequenced, but the actual rules and output format are deferred entirely to references/guideline.md; the body itself gives no executable detail, only pointers to read the reference file.

3 / 5

Workflow Clarity

A clear numbered sequence is given for the read-only review workflow, and the simple non-destructive task does not require the destructive/batch validation cap; minor validation gaps (e.g., confirming all rules were checked) keep it below 5.

4 / 5

Progressive Disclosure

The body is a clean overview pointing to a single one-level-deep, well-signaled reference (references/guideline.md, verified present) with an inline topic summary and easy navigation.

5 / 5

Total

15

/

20

Passed

Description

95%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 strong: it clearly states what the skill does, when to use it with natural trigger phrases, and where its boundaries are with explicit exclusions. Minor specificity deduction reflects that the listed actions are mostly variants of review/audit rather than genuinely distinct operations.

DimensionReasoningScore

Specificity

Names the domain and several concrete review actions (accessibility, design, UX, site best practices), but the actions are variants of the same review/audit operation rather than distinct capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (review UI code for Web Interface Guidelines compliance) and 'when' (Use when asked to...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes multiple natural user utterances as triggers ("review my UI", "check accessibility", "audit design", "review UX", "check my site against best practices"), giving comprehensive natural-language coverage.

5 / 5

Distinctiveness Conflict Risk

Provides a clear niche with distinct triggers plus explicit boundary guidance (Do NOT use for performance audits, SEO, or comprehensive site audits), minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.