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).
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(design)/web-design-guidelines/SKILL.mdQuality
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 skill description with excellent trigger terms, clear 'Use when' guidance, and notably good disambiguation through explicit negative boundaries referencing alternative skills. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., checking specific guidelines like accessibility, typography, spacing). Overall, it would perform very well in a multi-skill selection scenario.
Suggestions
Add 2-3 more specific concrete actions to the capability description, e.g., 'Checks color contrast, validates semantic HTML, reviews interaction patterns, audits responsive layout' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (UI code review for Web Interface Guidelines compliance) and mentions 'visual design and interaction patterns' but doesn't list multiple specific concrete actions like 'check color contrast, validate ARIA labels, review layout hierarchy'. | 2 / 3 |
Completeness | Clearly answers both what (review UI code for Web Interface Guidelines compliance, focusing on visual design and interaction patterns) and when (explicit 'Use when' clause with multiple trigger phrases), plus includes helpful negative boundaries for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'review my UI', 'check accessibility', 'audit design', 'review UX', 'check my site against best practices' — these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit negative boundaries ('Do NOT use for performance audits, SEO, or comprehensive site audits') and references to specific alternative skills, making it very unlikely to conflict with related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a well-structured dispatcher that correctly delegates detailed rules to an external reference file, but it suffers from internal redundancy (the workflow is stated twice) and lacks concrete examples of expected output. The actionability is limited because all substantive guidance lives in the external file, and the skill body itself provides no sample findings or executable examples to anchor Claude's behavior.
Suggestions
Remove the duplicate workflow — merge 'How It Works' and 'Usage' into a single section to eliminate redundancy and improve conciseness.
Add a concrete example of expected output (e.g., 2-3 sample findings in the `file:line` format) so Claude has an actionable template without needing to parse the external file first.
Add a brief validation step, such as confirming the guidelines file was successfully loaded before proceeding with the review.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy — the 'How It Works' and 'Usage' sections largely repeat the same 4-step process. The bullet list under 'Guidelines Reference' summarizing what the external file covers is borderline unnecessary since Claude will read the file anyway. Could be tightened. | 2 / 3 |
Actionability | The skill delegates all concrete guidance (rules, output format) to an external reference file. The skill itself contains no executable code, no concrete examples of findings output, and no specific rules — it's essentially a dispatcher to guideline.md. Without seeing that file, Claude gets only abstract direction from this content. | 2 / 3 |
Workflow Clarity | The steps are listed clearly and the sequence is logical, but there's no validation checkpoint (e.g., confirming the guidelines file was loaded successfully, handling cases where files don't match patterns, or verifying output completeness). The workflow is also stated twice redundantly. | 2 / 3 |
Progressive Disclosure | The skill appropriately keeps itself as a concise overview and delegates detailed rules to a single external reference file (references/guideline.md). The reference is clearly signaled and one level deep. The coverage summary helps with discovery. | 3 / 3 |
Total | 9 / 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
- tech-leads-club/agent-skills
- Commit
906a57d
- 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.