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".
85
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 strong description with excellent trigger terms and completeness. The explicit 'Use when' clause with multiple natural user phrases makes it highly discoverable. The main weakness is that the 'what' portion could be more specific about the concrete actions performed during the review.
Suggestions
Expand the capabilities portion to list specific review actions, e.g., 'Reviews UI code for Web Interface Guidelines compliance including accessibility checks, design pattern validation, and UX best practices.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI code, Web Interface Guidelines) and one action (review), but doesn't list multiple concrete actions like 'check color contrast, validate ARIA labels, audit navigation patterns'. | 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 | Clear niche focused on Web Interface Guidelines compliance specifically, with distinct triggers around UI review, accessibility, and design auditing that wouldn't conflict with general code review or other skills. | 3 / 3 |
Total | 11 / 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 concise and well-structured for its simple purpose, appropriately delegating detailed rules to an external source. However, it lacks concrete examples of the WebFetch tool usage and output format, and missing error handling guidance for fetch failures reduces its robustness.
Suggestions
Add a concrete example showing the exact WebFetch tool call syntax (e.g., `WebFetch({ url: '...' })`)
Include a brief example of the expected output format inline, even if the full format comes from the fetched guidelines
Add error handling guidance: what to do if the fetch fails or returns unexpected content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations. It assumes Claude knows how to fetch URLs and read files, providing only the essential workflow and source URL. | 3 / 3 |
Actionability | The skill provides a clear workflow but lacks concrete executable examples. It references 'WebFetch' without showing exact usage syntax, and the output format is delegated entirely to the fetched guidelines rather than shown inline. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. There's no guidance on what to do if the fetch fails, if guidelines are malformed, or how to handle files that can't be read. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the structure is appropriate. It clearly separates how it works, the source, and usage into distinct sections with no unnecessary nesting. | 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.
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.