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

64

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/data/02-designer-webguidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a concise, well-structured skill that effectively delegates the actual review rules to an external source, keeping the skill itself lightweight. However, the heavy reliance on an external fetch without any fallback, error handling, or inline examples of expected output means Claude has limited actionable guidance if the fetch fails. The workflow would benefit from a fallback mechanism and at least one concrete example of the expected output format.

Suggestions

Add a fallback or error handling step for when the WebFetch of the guidelines URL fails (e.g., 'If fetch fails, inform the user and suggest they provide the guidelines manually').

Include at least one concrete example of the expected output format (e.g., 'src/Button.tsx:42 — Missing aria-label on interactive element') so Claude knows the target format even without a successful fetch.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It doesn't explain what web interface guidelines are or how fetching works. Every section serves a clear purpose with no padding or unnecessary explanation.

3 / 3

Actionability

The skill provides a concrete URL and a clear process, but the actual review logic is entirely delegated to a fetched external document. There are no concrete code examples, specific rule checks, or example output formats within the skill itself—Claude must fetch and interpret the external content to know what to do.

2 / 3

Workflow Clarity

The steps are clearly sequenced (fetch → read → check → output), but there are no validation checkpoints. What happens if the fetch fails? What if the fetched content format changes? There's no error handling or verification step for the fetch operation, which is a critical dependency.

2 / 3

Progressive Disclosure

For a simple, short skill with no bundle files, the content is well-organized into clear sections (How It Works, Guidelines Source, Usage). The structure is appropriate for the skill's complexity and easy to navigate.

3 / 3

Total

10

/

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 a clear 'Use when' clause containing multiple natural trigger phrases, which is its strongest aspect. The main weakness is that the 'what' portion is somewhat vague — it says 'review UI code for compliance' but doesn't enumerate the specific checks or actions performed. The trigger terms, while natural, are broad enough that they could conflict with other accessibility or UX-focused skills.

Suggestions

Add specific concrete actions to the 'what' portion, e.g., 'Checks color contrast, semantic HTML, keyboard navigation, responsive layout, and ARIA usage against Web Interface Guidelines.'

Narrow some trigger terms to reduce conflict risk, e.g., specify 'Web Interface Guidelines' in the trigger clause or differentiate from general accessibility auditing tools.

DimensionReasoningScore

Specificity

It names the domain (UI code review) and the standard (Web Interface Guidelines compliance), but doesn't list specific concrete actions like 'check color contrast', 'validate ARIA labels', 'audit navigation patterns', etc.

2 / 3

Completeness

Clearly answers both 'what' (review UI code for Web Interface Guidelines compliance) and 'when' (explicit 'Use when' clause with multiple trigger scenarios).

3 / 3

Trigger Term Quality

Includes multiple natural trigger phrases users would actually say: 'review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices' — these cover a good range of natural user language.

3 / 3

Distinctiveness Conflict Risk

While 'Web Interface Guidelines compliance' is somewhat specific, terms like 'check accessibility' and 'review UX' could overlap with general accessibility audit skills or UX review skills. The specific standard helps but the trigger terms are broad enough to cause potential conflicts.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
majiayu000/claude-skill-registry
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.