CtrlK
BlogDocsLog inGet started
Tessl Logo

accessibility-compliance-accessibility-audit

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.

75

1.01x
Quality

61%

Does it follow best practices?

Impact

100%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/accessibility-compliance-accessibility-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The skill is well-structured and reasonably concise, with a clear sequenced workflow, but it lacks specific tooling detail and references a bundle file that is missing.

Suggestions

Name concrete tools for each step (e.g., axe-core/Lighthouse for automated scans, NVDA/VoiceOver for screen-reader checks) to make the guidance executable.

Create the referenced 'resources/implementation-playbook.md' or remove the broken reference so navigation resolves.

Drop the redundant restatement of the description in the opening paragraph or 'Context' section to tighten token use.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the opening paragraph and the 'Context' section both restate the frontmatter description, adding redundancy that could be tightened.

2 / 3

Actionability

The instructions give concrete categories ('Run automated scans', 'Perform manual checks (keyboard, screen reader, focus order, contrast)') but name no specific tools or commands, leaving the guidance incomplete for an instruction-only skill.

2 / 3

Workflow Clarity

Steps are clearly sequenced (scope → scans → manual checks → map findings → remediation + re-test) and mention a re-test loop, but validation checkpoints are implicit rather than explicit, matching the anchor for 2.

2 / 3

Progressive Disclosure

The body is well-organized with clear sections and a single signaled one-level reference, but the referenced 'resources/implementation-playbook.md' does not exist on disk, breaking the navigation the rubric asks us to verify.

2 / 3

Total

8

/

12

Passed

Description

72%

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 names a clear niche with concrete actions and natural trigger terms, but loses points for second-person voice and a missing explicit 'Use when...' trigger clause.

Suggestions

Rewrite in third person (e.g., 'Conducts accessibility audits...') to avoid the voice penalty.

Add an explicit trigger clause such as 'Use when auditing web or mobile experiences for WCAG compliance, identifying accessibility barriers, or preparing remediation guidance.'

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Conduct audits, identify barriers, and provide remediation guidance'), which would normally reach a 3, but it uses second-person voice ('You are an accessibility expert...'), which the rubric penalizes by reducing the specificity score by one.

2 / 3

Completeness

It clearly answers 'what' (audits, identify barriers, remediation) but has no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

It includes natural terms users would actually say — 'WCAG compliance', 'accessibility', 'inclusive design', 'audits', 'barriers' — giving good coverage of the phrasing a user reaches for when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The accessibility/WCAG-audit niche is clearly bounded with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.