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 with appropriate progressive disclosure by externalizing the actual guidelines. However, it lacks concrete executable examples for the WebFetch operation and has no error handling or validation steps for the fetch process, which could leave Claude uncertain in failure scenarios.
Suggestions
Add a concrete example of the WebFetch command or tool invocation to make the fetch step copy-paste ready
Include error handling guidance for when the guidelines URL is unreachable or returns invalid content
Add a brief example of the expected output format or reference that it's defined in the fetched content more explicitly
| 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 in 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 commands for WebFetch usage, and the actual rules are externalized. | 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 guidelines are malformed is not addressed. | 2 / 3 |
Progressive Disclosure | The skill appropriately delegates detailed rules to an external source (the fetched guidelines), keeping the SKILL.md as a concise overview. The reference is one level deep and clearly signaled. | 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.
6573f36
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.