rams

Run accessibility and visual design review on components. Use when reviewing UI code for WCAG compliance and design issues.

1.14x

Quality

81%

Does it follow best practices?

Impact

93%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill that efficiently delivers actionable accessibility and design review guidance through dense, scannable tables. The severity-tiered structure and concrete output format make it immediately usable. Minor weakness is the lack of explicit validation steps when Claude offers to fix issues directly.

Suggestions

Add a validation step in Guidelines for when Claude fixes issues: 'After applying fixes, re-run the review checklist on modified code to verify issues are resolved.'

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, using tables to compress information density. No unnecessary explanations of what accessibility or WCAG is—assumes Claude's competence and gets straight to actionable checklists.	3 / 3
Actionability	Highly actionable with specific code patterns to look for, exact WCAG references, concrete fixes for each issue, and a clear output format template. The tables provide copy-paste-ready patterns to match against.	3 / 3
Workflow Clarity	The guidelines section provides a basic sequence (read first, be specific, prioritize critical), but lacks explicit validation checkpoints. For a review task that could lead to code changes, there's no verify-after-fix loop mentioned.	2 / 3
Progressive Disclosure	Well-organized with clear sections (Mode, Accessibility Review with severity tiers, Visual Design Review, Output Format, Guidelines). Content is appropriately contained in a single file given its focused scope—no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 description has good structure with an explicit 'Use when...' clause and establishes a distinct niche around accessibility and WCAG compliance. However, it could be strengthened by listing more specific actions it performs and including additional natural trigger terms users commonly use when discussing accessibility.

Suggestions

Add specific concrete actions like 'check color contrast ratios', 'verify ARIA labels', 'audit keyboard navigation', 'review focus indicators'

Include common accessibility trigger terms users might say: 'a11y', 'screen reader', 'ADA', 'contrast', 'keyboard accessible', 'alt text'

Dimension	Reasoning	Score
Specificity	Names the domain (accessibility and visual design review) and mentions 'components' and 'UI code', but doesn't list specific concrete actions like 'check color contrast', 'verify keyboard navigation', or 'audit ARIA labels'.	2 / 3
Completeness	Clearly answers both what ('Run accessibility and visual design review on components') and when ('Use when reviewing UI code for WCAG compliance and design issues') with an explicit 'Use when...' clause.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'accessibility', 'WCAG', 'UI code', and 'design', but misses common variations users might say such as 'a11y', 'screen reader', 'ADA compliance', 'contrast ratio', or 'keyboard accessible'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'accessibility', 'WCAG compliance', and 'visual design review' creates a clear niche that is unlikely to conflict with general code review or other UI-related skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: brianlovin/claude-config
Commit: 1a9819e

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.