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".

58

Quality

66%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/web-design-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a lightweight wrapper that delegates nearly all substance to an externally fetched document. While concise in absolute terms, it repeats its core workflow twice and provides no fallback, examples, or validation steps. The actionability is limited because the skill contains no rules, no example output, and no error handling guidance.

Suggestions

Merge the 'How It Works' and 'Usage' sections to eliminate redundancy — they describe the same 4-step process.

Add an example of expected output format inline (e.g., `src/Button.tsx:42 — missing aria-label on interactive element`) so Claude knows the target format even if the fetch fails.

Add error handling guidance: what to do if the URL fetch fails (e.g., inform the user, retry, or use cached rules).

Include at least a few key rules inline as a fallback or summary, so the skill provides value even without successful URL retrieval.

DimensionReasoningScore

Conciseness

The content is relatively brief but has some redundancy — the 'How It Works' and 'Usage' sections largely repeat the same 4-step process. The explanation could be tightened by merging these sections.

2 / 3

Actionability

It provides a concrete URL to fetch and mentions using WebFetch, but the skill itself contains no executable code, no example output, and delegates all actual rule content and output format to an external URL. Claude doesn't know what rules to apply without fetching, making the skill dependent on runtime retrieval with no fallback.

2 / 3

Workflow Clarity

The steps are listed clearly and sequenced, but there's no validation checkpoint — no guidance on what to do if the fetch fails, if the guidelines format changes, or how to handle partial matches. For a review/audit workflow, there's no feedback loop for verification.

2 / 3

Progressive Disclosure

The skill is short and doesn't need external bundle files, but it has redundant sections (How It Works and Usage overlap significantly). There are no bundle files to reference, and the external URL dependency means the skill is essentially a thin wrapper with duplicated structure.

2 / 3

Total

8

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description with excellent trigger terms and completeness, clearly stating both what the skill does and when to use it. Its main weaknesses are the lack of specific concrete actions (what exactly does the review check?) and some potential overlap with general accessibility or UX review skills. Adding specific capabilities would strengthen both specificity and distinctiveness.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Checks color contrast ratios, validates semantic HTML, audits keyboard navigation, reviews responsive design patterns'

Differentiate from general accessibility or code review skills by emphasizing the specific Web Interface Guidelines framework and what makes it distinct from a generic a11y audit

DimensionReasoningScore

Specificity

It names the domain (UI code review) and the framework (Web Interface Guidelines compliance), but doesn't list specific concrete actions like 'check color contrast', 'validate ARIA labels', 'audit navigation patterns'. The description tells us the general activity but not the specific checks or outputs.

2 / 3

Completeness

Clearly answers both 'what' (review UI code for Web Interface Guidelines compliance) and 'when' (explicit 'Use when' clause with multiple trigger phrases). The when clause is explicit and well-structured.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms that users would actually say: 'review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices'. These cover multiple natural phrasings users might use.

3 / 3

Distinctiveness Conflict Risk

The triggers 'check accessibility' and 'review UX' could overlap with other accessibility-focused or UX review skills. However, the specific mention of 'Web Interface Guidelines compliance' provides some distinctiveness. The broad triggers like 'review my UI' could conflict with general code review skills.

2 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
freekmurze/dotfiles
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.