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".
81
Quality
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 ./data/02-designer-webguidelines/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 structure including an explicit 'Use when' clause. The main weakness is the lack of specific concrete actions in the capability statement - it tells us it reviews for compliance but doesn't enumerate what aspects it checks. The distinctiveness could also be improved by being more specific about what 'Web Interface Guidelines' means.
Suggestions
Add specific concrete actions to the capability statement, e.g., 'Reviews color contrast, ARIA labels, keyboard navigation, semantic HTML, and responsive layouts for Web Interface Guidelines compliance'
Clarify what 'Web Interface Guidelines' refers to (WCAG, internal standards, etc.) to improve distinctiveness from generic code review skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI code, Web Interface Guidelines) and the general action (review for compliance), but doesn't list specific concrete actions like 'check color contrast', 'validate ARIA labels', or '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 scenarios). The structure follows the recommended pattern. | 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 when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Web Interface Guidelines compliance' is somewhat specific, terms like 'review UX' and 'audit design' could overlap with general code review or design feedback 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 concise and well-structured for its simple purpose, appropriately delegating the actual rules to an external source. However, it lacks concrete examples of how to use WebFetch and has no error handling or validation steps for the fetch operation, which could cause issues if the external resource is unavailable or malformed.
Suggestions
Add a concrete example showing the WebFetch tool call syntax for retrieving the guidelines URL
Include a fallback or error handling step if the guidelines URL is unreachable
Specify what format the output findings should take if the fetched guidelines don't include format instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. Every section serves a clear purpose and assumes Claude understands how to fetch URLs and process files. | 3 / 3 |
Actionability | Provides a clear URL and general workflow, but lacks concrete code examples for fetching or parsing. The instruction to 'Use WebFetch' is vague without showing the actual command or API call. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No guidance on what to do if the fetch fails, if the guidelines format changes, or how to handle parsing errors. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the structure is appropriate. Clear sections with logical organization, and the external guidelines are referenced at one level deep via URL. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- majiayu000/claude-skill-registry-data
- Commit
2bbaa03
- 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.