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

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

A compact, well-organized adapter skill that delegates the actual rules to a fetched source. It earns full marks for progressive disclosure but loses points for duplicated step lists, abstract checking guidance, and a missing fetch-failure checkpoint.

Suggestions

Collapse the 'How It Works' and 'Usage' sections into a single numbered workflow to remove the duplicated fetch/read/apply/output step lists.

Add a validation checkpoint for the network fetch (e.g., what to do if WebFetch fails or returns unexpected content) so the workflow has an explicit error-recovery loop.

Replace the abstract 'Apply all rules from the fetched guidelines' with more concrete guidance on how findings should be matched and reported, or clarify that the fetched document fully defines the checking procedure.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the 'How It Works' and 'Usage' sections repeat nearly identical four-step lists (fetch, read, apply rules, output), which could be consolidated; not quite 'every token earns its place'.

2 / 3

Actionability

It gives concrete process details (exact source URL, the WebFetch tool, the terse file:line output format), but the core instruction 'Check against all rules' / 'Apply all rules' is abstract and delegates the substantive logic to the fetched content, leaving key details implicit.

2 / 3

Workflow Clarity

Steps are clearly numbered and sequenced, but the workflow depends on a fragile external network fetch with no validation checkpoint or error-recovery guidance for a failed/unreachable fetch, so it stops short of explicit feedback loops.

2 / 3

Progressive Disclosure

At under 50 lines with no bundle files, it is organized into clear sections (How It Works, Guidelines Source, Usage) and its one external reference (../ui-design/SKILL.md) is clearly signaled and a single level deep, satisfying the simple-skill bar.

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.

A strong, third-person description with an explicit trigger clause and natural user phrasing. Its only weakness is that it names a single action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

It names the domain ('UI code', 'Web Interface Guidelines compliance') and a concrete action ('Review'), but lists only a single action rather than multiple specific concrete actions, so it falls short of the top anchor.

2 / 3

Completeness

It explicitly states what the skill does ('Review UI code for Web Interface Guidelines compliance') and provides an explicit 'Use when...' trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

The 'Use when' clause supplies natural phrases users would actually say — 'review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (external Web Interface Guidelines audit) with distinct triggers, and the body explicitly separates it from the sibling ui-design skill, making wrong-skill activation unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
EpicenterHQ/epicenter
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.