accessibility-specialist

Skill dedicada a acessibilidade digital. Use quando precisar revisar WCAG, teclado, screen reader, contraste, semantica, motion reduction e acessibilidade de formularios, componentes e fluxos.

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/22-accessibility-specialist/SKILL.md

Quality

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 description has strong trigger term coverage and clear 'Use when' guidance, making it easy for Claude to identify when to select this skill. However, it lacks specificity about concrete actions - it only mentions 'revisar' (review) without detailing what specific tasks the skill enables (e.g., audit compliance, generate reports, fix issues, test with assistive technology).

Suggestions

Replace the vague 'revisar' with specific concrete actions like 'auditar conformidade WCAG', 'identificar problemas de contraste', 'gerar relatórios de acessibilidade', or 'corrigir problemas de navegação por teclado'

Add 2-3 specific deliverables or outputs the skill produces (e.g., 'accessibility audit reports', 'ARIA attribute recommendations', 'color contrast fixes')

Dimension	Reasoning	Score
Specificity	Lists domain areas (WCAG, keyboard, screen reader, contrast, semantics, motion reduction, forms, components, flows) but doesn't describe concrete actions - only mentions 'revisar' (review) as a vague action without specifying what reviewing entails.	2 / 3
Completeness	Explicitly answers both what ('Skill dedicada a acessibilidade digital') and when ('Use quando precisar revisar...') with clear trigger guidance listing specific accessibility concerns that should activate this skill.	3 / 3
Trigger Term Quality	Includes good coverage of natural accessibility-related terms users would say: 'WCAG', 'teclado' (keyboard), 'screen reader', 'contraste', 'semantica', 'motion reduction', 'acessibilidade', 'formularios', 'componentes'. These are terms practitioners naturally use.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on digital accessibility with distinct technical triggers (WCAG, screen reader, contrast, motion reduction) that are unlikely to conflict with other skills - accessibility is a well-defined domain.	3 / 3
	Total	11 / 12 Passed

Implementation

35%

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

This skill functions more as a role description than actionable guidance. It defines when to use the skill and what outputs to expect, but lacks concrete techniques, code examples, or specific testing procedures for accessibility validation. The checklist items are too abstract to be immediately actionable.

Suggestions

Add concrete code examples for common accessibility checks (e.g., testing focus order with JavaScript, checking ARIA attributes, contrast ratio validation commands)

Include specific screen reader testing commands or browser DevTools accessibility audit steps

Provide example findings format showing how to document and prioritize accessibility issues

Add a step-by-step workflow with explicit validation checkpoints (e.g., 'Run axe-core -> Review violations -> Test with keyboard -> Verify with screen reader')

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary governance references and meta-information that Claude doesn't need explained. The checklist items are appropriately brief.	2 / 3
Actionability	The skill provides abstract checklists and categories but no concrete code, commands, or executable examples. Items like 'navegacao por teclado completa' describe what to check but not how to check it.	1 / 3
Workflow Clarity	There's an implicit workflow (inputs -> checklist -> outputs -> handoff) but no explicit sequencing, validation steps, or feedback loops for the accessibility review process itself.	2 / 3
Progressive Disclosure	References to external files (GLOBAL.md, policies/, templates/) are present but the skill itself lacks concrete content - it's mostly pointers without substantive quick-start material.	2 / 3
	Total	7 / 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: felvieira/claude-skills-fv
Commit: 524725e

Reviewed: 5 days 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.