ux-ui-a11y
접근성 검사 에이전트. 웹 접근성을 검사하고 개선합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill ux-ui-a11y37
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/skillValidation for skill structure
Discovery
22%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 is too brief and vague to effectively guide skill selection. It lacks specific concrete actions, natural trigger terms users would say, and completely omits guidance on when Claude should use this skill. The Korean language description needs significant expansion to be useful in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with trigger terms like 'accessibility audit', 'WCAG', 'a11y', 'screen reader compatibility', '접근성 검사'
List specific concrete actions such as 'Validates WCAG 2.1 compliance, checks color contrast ratios, audits alt-text for images, identifies keyboard navigation issues'
Include common file types or contexts like 'HTML pages', 'React components', 'web applications' to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language - '웹 접근성을 검사하고 개선합니다' (checks and improves web accessibility) names only two abstract actions without specifying concrete capabilities like WCAG compliance checking, alt-text validation, or color contrast analysis. | 1 / 3 |
Completeness | Only provides a weak 'what' (checks and improves accessibility) with no 'when' clause or explicit trigger guidance. Missing any 'Use when...' equivalent to indicate when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains '접근성' (accessibility) and '웹' (web) which are relevant keywords, but misses common variations users might say like 'WCAG', 'a11y', 'screen reader', 'ADA compliance', or specific accessibility issues. | 2 / 3 |
Distinctiveness Conflict Risk | The term '접근성 검사' (accessibility check) provides some specificity to web accessibility domain, but could overlap with general web development, testing, or audit skills without clearer boundaries. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a role description rather than actionable guidance. It lists what an accessibility agent should do but provides zero concrete instructions on how to perform accessibility testing, what tools to use, what WCAG criteria to check, or how to generate reports. The content needs substantial expansion with executable examples and specific testing procedures.
Suggestions
Add concrete code examples for accessibility testing (e.g., using axe-core, pa11y, or lighthouse CLI commands)
Include specific WCAG criteria to check with examples of compliant vs non-compliant code patterns
Define a clear workflow: scan -> identify issues -> categorize by severity -> generate report with fix recommendations
Add example output format for the accessibility report that should be generated in docs/accessibility/
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude knows, but it's essentially just a list of responsibilities without actionable content - it's lean but empty rather than efficiently informative. | 2 / 3 |
Actionability | No concrete code, commands, tools, or executable guidance provided. Only vague task descriptions like 'WCAG 준수 검사' without any specifics on how to actually perform these checks. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or process defined. Just a list of responsibilities with no steps, validation checkpoints, or guidance on how to conduct accessibility testing. | 1 / 3 |
Progressive Disclosure | The content is short and organized into clear sections, but it references an output location without providing any linked resources for detailed guidance on WCAG standards, tools, or testing procedures. | 2 / 3 |
Total | 6 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.