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

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/public/web-design-guidelines/SKILL.md

The canonical home for this skill is pleaseai/web-design

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 compact, well-structured skill that delegates its rules to a fetched remote source, keeping the body lean. Its weakness is actionability and workflow robustness: the executable detail lives in an external file with no validation or error-handling guidance for the fetch step.

Suggestions

Add a fallback or validation step for the fetch (e.g., what to do if WebFetch fails or returns unexpected content) so the workflow is robust without external dependence.

Inline one or two representative rules or a sample output so the skill remains actionable even when the remote source is unavailable.

Consolidate the overlapping 'How It Works' and 'Usage' step lists to remove the duplicated fetch-read-apply-output sequence and tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining basic concepts, but the 'How It Works' and 'Usage' sections duplicate the same fetch-read-apply-output workflow, a minor instance of padding that could be trimmed.

4 / 5

Actionability

It gives a concrete source URL, names WebFetch, and specifies the output format ('file:line'), but the actual rules and detailed output instructions live in a remotely fetched file, leaving key execution details external and incomplete rather than self-contained.

3 / 5

Workflow Clarity

Steps are clearly sequenced (fetch, read, apply, output) with a conditional branch for missing files, but there is no validation or feedback checkpoint (e.g., handling a failed fetch), leaving checkpoints implicit.

3 / 5

Progressive Disclosure

This is a short single-purpose skill under 50 lines with no bundle files, and its content is well-organized into clear sections with a single one-level-deep reference (the guidelines URL), matching the simple-skill exception for a top score.

5 / 5

Total

15

/

20

Passed

Description

78%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 clearly states its purpose and provides concrete, natural trigger phrases for when to invoke it. The main gap is specificity — it relies on one broad action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('Review UI code for Web Interface Guidelines compliance') with one concrete action (review/check compliance), but does not enumerate multiple distinct actions, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

It explicitly states both what it does ('Review UI code for Web Interface Guidelines compliance') and when to use it via concrete trigger phrases, matching the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor.

5 / 5

Trigger Term Quality

It quotes several natural phrases users would say ('review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices'), giving good keyword coverage, though a few synonyms are missing relative to the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Web Interface Guidelines compliance' niche with UI/UX/accessibility triggers is mostly distinct with minimal conflict risk, though it could overlap slightly with a generic accessibility-audit skill, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

16

/

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
bytedance/deer-flow
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.