CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 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".

72

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A high-quality, highly actionable skill body with concrete code, exact tooling, numeric WCAG thresholds, and an audit workflow that includes an explicit feedback loop and completion-evidence checklist. Its main weakness is progressive disclosure: it points to many policy/template/script files that are absent from this bundle, leaving those references unverifiable.

Suggestions

Ship the referenced files (at minimum `scripts/check-contrast.mjs` and `templates/accessibility-check.md`) inside the skill's scripts/ and references/ directories, or remove/inline the references — the contrast-check command is presented as the canonical verification gate but has no backing file in the bundle.

Convert bare path mentions like `policies/handoffs.md` and `templates/accessibility-check.md` into clearly signaled, one-level-deep links (e.g., "See [templates/accessibility-check.md](templates/accessibility-check.md)") so navigation to detail files is explicit rather than buried in prose.

Tighten the Handoff section: the two long paragraphs about skills 56 and 57 restate overlapping scope boundaries and could be reduced to two lines each, trimming the main token overhead in an otherwise lean body.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — numeric thresholds ("4.5:1 texto normal, 3:1 texto grande"), tool names with exact packages, and a prioritized "criterios que mais quebram" checklist rather than a full WCAG dump — but the governance section and the two long handoff paragraphs (skills 56/57) add prose that could be trimmed, landing it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is copy-paste ready and covers common cases: complete ERRADO/CERTO HTML/CSS snippets (aria-label on icon buttons, aria-describedby error linking, prefers-reduced-motion media query), exact tool invocations ("@axe-core/playwright", "jest-axe", "NVDA (Win, gratis) ou VoiceOver (Mac, Cmd+F5)"), and a runnable verification command (`node scripts/check-contrast.mjs <css>`).

5 / 5

Workflow Clarity

The "Checkpoint" paragraph gives an explicit sequence — run the 4 test categories in table order, turn each finding into a concrete fix, apply, then re-run only the failed category — with a genuine feedback loop that even distinguishes symptom from cause ("fix cobriu o sintoma... mas nao a causa"), reinforced by the "Evidencia de Conclusao" validation checklist.

5 / 5

Progressive Disclosure

Sections are well organized and the inline prioritized checklist is appropriately sized for SKILL.md, but the body references a dozen files — `GLOBAL.md`, `policies/execution.md`, `policies/handoffs.md`, `scripts/check-contrast.mjs`, `templates/accessibility-check.md`, `memory/constitution.md` — and none of them exist in the bundle (no references/, scripts/, or assets/ directories are present), so the references are neither verifiable nor clearly signaled as one-level-deep navigations.

3 / 5

Total

17

/

20

Passed

Description

95%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.

A strong description: explicit what-and-when structure, a rich bilingual trigger list with synonyms, and a well-scoped a11y niche. The only minor gap is reliance on one verb ("revisar") rather than a wider variety of concrete action verbs.

DimensionReasoningScore

Specificity

The description lists several concrete action areas — "revisar WCAG, teclado, screen reader, contraste, semantica, motion reduction e acessibilidade de formularios, componentes e fluxos" — but leans on a single verb ("revisar") across domains rather than multiple distinct actions, so it falls just short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both questions: "what" ("Skill dedicada a acessibilidade digital... revisar WCAG, teclado, screen reader, contraste, semantica...") and "when" ("Use quando precisar revisar..." plus a separate explicit "Trigger em:" list of concrete trigger phrases), matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The dedicated trigger list covers natural terms with bilingual synonyms and abbreviations: "acessibilidade", "accessibility", "a11y", "WCAG", "screen reader", "leitor de tela", "navegacao por teclado", "contraste de cor", "ARIA", "semantica HTML", "motion reduction", "audit de acessibilidade" — matching the comprehensive-synonyms anchor exactly.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (digital accessibility / WCAG auditing) with distinct, a11y-only trigger terms; no generic wording like "helps with frontend" that would pull in sibling UI/UX or Frontend skills, so conflict risk is minimal.

5 / 5

Total

19

/

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.