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".
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/web-design-guidelines-2/SKILL.mdQuality
Discovery
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 term coverage and complete what/when structure. The main weakness is the lack of specific concrete actions beyond 'review' - listing specific checks (accessibility audits, responsive design, semantic HTML) would strengthen specificity and distinctiveness.
Suggestions
Add 2-3 specific concrete actions like 'checks color contrast ratios, validates semantic HTML structure, audits keyboard navigation' to improve specificity
Consider adding file type triggers like '.html', '.css', 'React components' to further distinguish from general design review skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI code, Web Interface Guidelines) and one action (review), but lacks specific concrete actions like 'check color contrast', 'validate ARIA labels', or 'audit responsive breakpoints'. | 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). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices' - these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Web Interface Guidelines compliance' is specific, terms like 'review UX' and 'audit design' could overlap with general code review or design system skills. The accessibility focus helps but isn't exclusive. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, appropriately delegating detailed guidelines to an external source. However, it lacks concrete executable examples for the fetch operation and has no error handling or validation steps for when the external URL might be unavailable or return unexpected content.
Suggestions
Add a concrete example of the WebFetch tool call syntax to make the fetch step immediately actionable
Include fallback behavior or error handling guidance for when the guidelines URL is unavailable
Add a brief example of what the output format looks like (even if details are in the external file) to set expectations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. Every section serves a clear purpose and assumes Claude's competence with fetching URLs and processing files. | 3 / 3 |
Actionability | The skill provides a clear workflow but lacks concrete executable examples. It references fetching guidelines and applying rules but doesn't show actual code or command syntax for WebFetch, and defers all rule details to an external URL. | 2 / 3 |
Workflow Clarity | Steps are listed clearly (fetch, read, check, output), but there are no validation checkpoints or error handling guidance. What happens if the fetch fails or the URL is unavailable is not addressed. | 2 / 3 |
Progressive Disclosure | The skill appropriately delegates detailed rules to an external source while keeping the SKILL.md as a concise overview. The structure is clear with well-organized sections and a single-level reference to external content. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
7d77bd2
Table of Contents
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.