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".
Install with Tessl CLI
npx tessl i github:jdrhyne/agent-skills --skill web-design-guidelines84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 well-crafted description with strong trigger terms and explicit 'Use when' guidance. The main weakness is the somewhat generic capability statement - it could benefit from listing specific review actions (accessibility checks, design pattern validation, etc.) to better communicate the skill's concrete capabilities.
Suggestions
Expand the capability statement to list specific review actions, e.g., 'Review UI code for Web Interface Guidelines compliance including accessibility checks, responsive design patterns, and semantic HTML validation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI code, Web Interface Guidelines) and the action (review for compliance), but doesn't list multiple specific 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 with specific UI/UX/accessibility triggers; unlikely to conflict with general code review or other document 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 doesn't address error scenarios like failed fetches or unavailable guidelines.
Suggestions
Add a concrete example showing WebFetch tool invocation syntax (e.g., the exact tool call format)
Include a brief example of the expected output format rather than fully delegating to external guidelines
Add a fallback instruction for when the guidelines URL is unreachable
| 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, and the output format is delegated entirely to the fetched guidelines rather than providing a concrete example. | 2 / 3 |
Workflow Clarity | Steps are listed clearly (fetch, read, check, output), but there's no validation checkpoint or error handling guidance. What happens if the fetch fails or guidelines are unavailable is not addressed. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the structure is appropriate. It provides a clear overview with the external guidelines URL as the single reference point, avoiding 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.
- 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.