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

62

Quality

73%

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 ./.claude/skills/web-design-guidelines/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is brief and well-structured but leans heavily on an external fetch for its core rules, which weakens actionability and leaves the fragile fetch step without validation. Sectional duplication of the workflow steps is the main conciseness drain.

Suggestions

Merge the near-duplicate "How It Works" and "Usage" step lists into a single workflow to remove redundancy and tighten the token budget.

Inline the most important compliance rules (or a stable subset) so the skill remains actionable when the external URL is unreachable, and add a fallback for fetch failure.

Add a brief validation/checkpoint note for the external fetch step (e.g., verify the fetch succeeded and contains expected rule sections before applying).

DimensionReasoningScore

Conciseness

The body is lean and free of concept-explanation fluff, but the "How It Works" and "Usage" sections repeat the same fetch→read→apply→output sequence nearly verbatim, so not every token earns its place; matches the 'mostly efficient but could be tightened' anchor rather than 3.

2 / 3

Actionability

It gives a concrete command (fetch a specific URL via WebFetch) and an output format, but offloads the actual rules to an external URL with only "apply all rules from the fetched guidelines," leaving key detail unspecified; matches 'some concrete guidance but incomplete; missing key details' rather than 3.

2 / 3

Workflow Clarity

Steps are clearly numbered (1–4) and the task is read-only review, but the fragile external-fetch step has no validation or fallback (e.g., what to do if WebFetch fails or the URL moves), so checkpoints are missing/implicit per the score-2 anchor.

2 / 3

Progressive Disclosure

It is a short, well-organized single-file skill with clearly signaled one-level-deep navigation (the single external URL); with no bundle files and no nested references, the simple-skill note allows a 3 for clear organization.

3 / 3

Total

9

/

12

Passed

Description

90%

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 states a concrete purpose, includes an explicit "Use when" trigger clause with natural, varied phrasings, and carves out a distinct niche. The only weakness is specificity, since it names essentially one action (compliance review) rather than enumerating several distinct concrete capabilities.

DimensionReasoningScore

Specificity

"Review UI code for Web Interface Guidelines compliance" names the domain and a review action but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor; not 3 because there is no enumeration of several specific actions, and not 1 because the language is concrete rather than vague.

2 / 3

Completeness

It explicitly answers what ("Review UI code for Web Interface Guidelines compliance") and when (an explicit "Use when asked to..." clause with concrete triggers), satisfying the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Natural quoted phrases users would actually say are well covered: "review my UI", "check accessibility", "audit design", "review UX", and "check my site against best practices", matching the 'good coverage of natural terms users would say' anchor.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Web Interface Guidelines compliance) with distinctive trigger phrases unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
revokslab/ShipFree
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.