CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

accessibility-specialist

Skill dedicada a acessibilidade digital. Trigger em: "acessibilidade", "accessibility", "a11y", "WCAG", "screen reader", "navegacao por teclado", "contraste de cor", "ARIA", "semantica HTML", "motion reduction", "leitor de tela", "audit de acessibilidade".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/22-accessibility-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

This is a strong operational skill body: it converts a broad standard (WCAG 2.2 AA) into numbered criteria, exact thresholds, executable fix patterns, and a re-validation loop with evidence requirements. The workflow and actionability are exemplary; the only real gaps are minor verbosity and references to files that are not shipped in the bundle.

DimensionReasoningScore

Conciseness

The body is dense and normative — numbered WCAG criteria, exact thresholds, and tool names with almost no education of concepts Claude already knows. Minor trimmable fat keeps it below anchor 5: the motivational opener ('Acessibilidade nao e um check cosmetico de ultima hora...'), the contrast-script guidance split across two adjacent paragraphs (blockquote plus the 'Para duas cores opacas' paragraph), and the wordy overlap notes for skills 56/57 in the Handoff section.

4 / 5

Actionability

Guidance is fully executable: copy-paste HTML/CSS fix snippets for the most common violations, runnable commands ('node scripts/check-contrast.mjs <css>', the contrast.mjs pair-checker with its thresholds), exact numeric criteria (4.5:1, 3:1, 24x24px, 320px, 200%), and named tools with activation keys (NVDA, VoiceOver Cmd+F5). These cover the common cases the skill targets.

5 / 5

Workflow Clarity

The Checkpoint paragraph gives an explicit sequence (run the 4 categories in table order) with a validate->fix->re-run-only-the-failed-category feedback loop, plus symptom-vs-cause recovery guidance when an automated fix passes but keyboard testing still fails. The 'Evidencia de Conclusao' section adds a completion gate and the WCAG checklist makes the process auditable — matching anchor 5's feedback loops and checklists.

5 / 5

Progressive Disclosure

The single file is well-organized into scannable sections (when to use/not use, inputs/outputs, test matrix, checklist, examples, handoffs) and all file references are one level deep and clearly signaled. It misses anchor 5 because none of the referenced files (GLOBAL.md, policies/*.md, scripts/check-contrast.mjs, templates/accessibility-check.md, skills/91-unslop/...) exist in the skill's bundle — from this bundle's perspective they are dangling pointers, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

63%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description's strongest asset is its bilingual, synonym-rich trigger list, which clearly answers when to invoke the skill. Its main weakness is the capability statement: 'Skill dedicada a acessibilidade digital' names the domain without a single concrete action, leaving a reader unable to tell whether the skill audits, fixes, teaches, or specifies. Overall it lands slightly above the midpoint of the scale.

Suggestions

Replace 'Skill dedicada a acessibilidade digital' with 2-3 concrete action verbs that state what the skill actually does, e.g. 'Audita fluxos e componentes contra WCAG 2.2 AA, prioriza gaps por impacto x esforco e especifica correcoes concretas de ARIA/teclado/contraste'.

Fold the trigger terms into a 'Use when...' style clause (e.g. 'Use quando o usuario mencionar acessibilidade, a11y, WCAG, screen reader...') so 'what' and 'when' read as one complete sentence pair rather than a label plus a keyword list.

Add the highest-volume natural phrases currently missing from the trigger list — 'alt text', 'focus visible'/'foco', and 'keyboard only'/'so teclado' — to catch phrasings users commonly say.

DimensionReasoningScore

Specificity

The only capability statement is "Skill dedicada a acessibilidade digital" — it names a specific domain but lists zero concrete actions (no auditing, reviewing, or fixing verbs anywhere in the description). It sits above anchor 1 (the domain is narrow, not 'documents'-generic) but below anchor 3, which requires 1-2 concrete actions; none are explicitly stated.

2 / 5

Completeness

"Trigger em: ..." provides explicit trigger guidance (so the missing-Use-when cap of 3 is not the binding constraint — it genuinely answers 'when'), but the 'what' is answered only at domain level with no stated actions, scoring what is explicitly written rather than inferring audit/review capabilities from the domain. It does not reach anchor 4 because that anchor's example pairs a concrete 'what' with the weaker 'when'; here the 'what' is the weak half.

3 / 5

Trigger Term Quality

Twelve explicit trigger terms span both English and Portuguese with the abbreviation "a11y" and natural synonyms ("screen reader" / "leitor de tela", "accessibility" / "acessibilidade"), matching the comprehensive synonym coverage of anchor 5. Only trivially related terms (e.g., 'alt text') are absent, which does not pull it to anchor 4.

5 / 5

Distinctiveness Conflict Risk

A clear accessibility niche with distinct triggers ("WCAG", "ARIA", "a11y", "leitor de tela") gives minimal conflict risk, but "semantica HTML" and "contraste de cor" are terms a frontend or design skill could equally claim. Anchor 5 would require all triggers to be unambiguously owned by this skill.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/22-accessibility-specialist/SKILL.md

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.