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

Optimize this skill with Tessl

npx tessl skill review --optimize ./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 bulk of its rules to an external source. Its main weaknesses are the lack of concrete output examples and missing error handling for the external fetch dependency. The actionability suffers because the skill is essentially a wrapper around fetched content with no fallback or sample output.

Suggestions

Add an example of expected output format (e.g., `src/Button.tsx:42 — missing aria-label on interactive element`) so Claude knows what to produce even before fetching guidelines.

Add a fallback or error handling step: what should Claude do if the URL fetch fails or returns unexpected content?

Specify which tool to use for fetching (e.g., exact MCP tool name or bash curl command) to make the fetch step fully executable.

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 purpose with no padding or unnecessary explanation.

3 / 3

Actionability

The skill provides a concrete URL and a clear process, but the actual rules and output format are entirely delegated to the fetched content. There's no example of what the output looks like, no concrete code for fetching, and no fallback if the URL is unavailable. The guidance is specific but not fully self-contained or executable.

2 / 3

Workflow Clarity

Steps are listed clearly and sequenced, but there's no validation checkpoint — no guidance on what to do if the fetch fails, if the fetched content is malformed, or how to handle files that can't be read. For an operation that depends on an external URL, error handling/fallback is important but missing.

2 / 3

Progressive Disclosure

For a simple skill with no bundle files, the content is well-organized into clear sections (How It Works, Guidelines Source, Usage). The external reference to the guidelines URL is one level deep and clearly signaled. The skill appropriately delegates detailed rules to the external source rather than inlining them.

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 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 other accessibility or UX review skills. Adding more 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 layout patterns'

Differentiate from general accessibility tools by emphasizing what makes 'Web Interface Guidelines' distinct, e.g., referencing specific guideline categories or unique aspects of the framework

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 stays at a high level of 'review' without detailing what aspects are checked.

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 would use.

3 / 3

Distinctiveness Conflict Risk

Terms like 'check accessibility' and 'review UX' could overlap with general accessibility auditing skills or UX review skills. The 'Web Interface Guidelines' reference adds some specificity, but the trigger terms are broad enough to potentially conflict with other UI/UX-related skills.

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