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". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The content is a well-structured overview that practices good progressive disclosure and has a clear review workflow. Its main weaknesses are repeated step lists that reduce conciseness and actionability guidance that depends on an external reference file rather than being self-contained.

Suggestions

Consolidate the near-duplicate step lists in "How It Works" and "Usage" into a single workflow section to remove repetition and improve conciseness.

Add one or two concrete example findings in the `file:line` output format in the body so the guidance is actionable without requiring the reference file.

Use one consistent reference syntax (either the `#[[file:...]]` form or a plain relative path) throughout the body to avoid the current inconsistency.

DimensionReasoningScore

Conciseness

The body is lean and explains no background concepts, but it restates essentially the same four-step process (read guidelines, read files, apply rules, output findings) in both "How It Works" and "Usage", which could be tightened; this sits below the fully-lean score-3 anchor and above the verbose score-1 anchor.

2 / 3

Actionability

It gives some concrete directives (read from a specific path, output in `file:line` format, group by file), but the actual executable review rules are externalized to the reference file rather than being self-contained in the body, matching the "some concrete guidance but incomplete" anchor.

2 / 3

Workflow Clarity

The sequence (read guidelines, read files, check rules, output findings) is clear and unambiguous, and includes a user-interaction checkpoint ("If no files specified, ask the user"); as a read-only review task it has no destructive or batch operations that would require validation, so it is not capped at 2.

3 / 3

Progressive Disclosure

The body is a concise overview that delegates all detailed rules to a single one-level-deep, clearly signaled reference at references/guideline.md (verified to exist), with a topic list aiding discovery, matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

10

/

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 uses correct third-person voice, answers both what and when with explicit natural trigger phrases, and actively disambiguates from neighboring skills. Its only relative weakness is specificity, since it describes one core action (review/audit) rather than enumerating several distinct concrete capabilities.

DimensionReasoningScore

Specificity

"Review UI code for Web Interface Guidelines compliance" and "Focuses on visual design and interaction patterns" name the domain and a concrete action, but do not enumerate multiple distinct concrete actions, so this is below the score-3 anchor and above the vague score-1 anchor.

2 / 3

Completeness

It states what ("Review UI code for Web Interface Guidelines compliance") and gives an explicit "Use when asked to..." trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

"Use when asked to 'review my UI', 'check accessibility', 'audit design', 'review UX', or 'check my site against best practices'" provides strong coverage of natural phrases a user would actually say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The explicit "Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit)" disambiguation plus distinct triggers give it a clear niche unlikely to conflict with other skills.

3 / 3

Total

11

/

12

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
tech-leads-club/agent-skills
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.