CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-ada-web-accessibility

Audit and document web accessibility to mitigate US ADA Title II/III litigation and meet DOJ compliance deadlines. Use when: Classify legal exposure under ADA Title II/III and state laws; Prioritize web fixes based on common US litigation patterns; Generate defensible US-flavor accessibility statements and plans.

Quality

55%

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/nex-ada-web-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a product landing page rather than skill instructions: it markets capabilities ('What it does', 'Why this beats prompting it yourself', purchase FAQ) while omitting every artifact needed to execute them — the audit checklist, the legal fact base, the playbooks, and the templates are all absent. An agent loading this skill learns nothing about how to actually perform the audit or generate the documents. The description is strong, but the content delivers almost none of it.

Suggestions

Replace the marketing sections ('The problem', 'Why this beats prompting it yourself', the 'Questions' FAQ) with operational content: the actual 50-point WCAG 2.1 AA checklist with pass/fail criteria, or a reference file containing it.

Add a step-by-step workflow — intake (entity type: Title II vs Title III vs 508/Unruh), audit execution, exposure classification, prioritized remediation plan, document generation — with validation checkpoints (e.g. counsel review before issuing legal artifacts).

Include the demand-letter response playbook and accessibility statement / remediation plan templates as concrete, fillable examples in the body or as clearly signaled reference files, since the body currently claims these artifacts but provides none.

DimensionReasoningScore

Conciseness

Noticeably padded with sections that add no operational value: 'Why this beats prompting it yourself', a purchase-oriented FAQ ('What specific assets are included when I purchase this skill', 'How are updates handled...'), and a promotional footer linking a paid catalog. Not 1 because it does not explain concepts Claude already knows — the padding is marketing copy, not basic-concept tuition.

2 / 5

Actionability

Entirely descriptive with no executable guidance: no audit checklist, no prioritization criteria, no commands, no templates, and it explicitly states 'Scripts, extension source, and templates from the original package are not in this folder'. The 'Executes a 50-point WCAG 2.1 AA audit' claim is never backed by the actual 50 points — it only describes rather than instructs.

1 / 5

Workflow Clarity

No multi-step process is ever sequenced: there are no steps for conducting the audit, classifying legal exposure, prioritizing fixes, or generating the statement/remediation plan/response playbook artifacts, and no validation checkpoints anywhere. The 'Example' section shows a sample answer without any procedure for producing it.

1 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the materials the body repeatedly claims — '50-point WCAG 2.1 AA check-list', 'demand letter response playbooks', 'verified 2026 legal fact base', 'compliance documentation templates' — are neither inlined nor referenced via navigable pointers. The section headers are organized, but there is effectively nothing to disclose at any level, matching the minimal-structure anchor.

2 / 5

Total

6

/

20

Passed

Description

78%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 is well-formed: it states what the skill does with several concrete actions, includes an explicit 'Use when:' clause, and carves out a distinct niche. Its main gaps are missing common trigger synonyms (WCAG, Section 508, demand letter) and 'when' triggers phrased as commands rather than natural user situations.

Suggestions

Rewrite the 'Use when:' clause around concrete user situations, e.g. 'Use when the user receives an ADA demand letter, asks about WCAG/Section 508 compliance, or must meet DOJ Title II deadlines'.

Add missing natural trigger terms users would say: 'WCAG', 'Section 508', 'lawsuit', 'demand letter', 'accessibility audit'.

Mention the concrete audit mechanism (50-point WCAG 2.1 AA audit) in the description to sharpen the 'what'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Audit and document web accessibility', 'Classify legal exposure under ADA Title II/III and state laws', 'Prioritize web fixes based on common US litigation patterns', 'Generate defensible US-flavor accessibility statements and plans' — matching the 'several specific actions; minor gaps' anchor. Not 5 because the actions remain high-level: the concrete audit mechanism (50-point WCAG 2.1 AA audit) appears only in the body, not the description.

4 / 5

Completeness

Explicitly answers both 'what' ('Audit and document web accessibility to mitigate US ADA Title II/III litigation and meet DOJ compliance deadlines') and 'when' via an explicit 'Use when:' clause. Below anchor 5 because the 'when' triggers are phrased as capability commands ('Classify legal exposure...') rather than concrete user situations or trigger phrases a user would naturally say.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'web accessibility', 'ADA Title II/III', 'litigation', 'DOJ compliance deadlines', 'accessibility statements'. Falls short of anchor 5 because common variations users would say — 'WCAG', 'Section 508', 'lawsuit', 'demand letter' — are absent; clearly above anchor 3 since coverage is more than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — US ADA web accessibility litigation and DOJ compliance — with distinct trigger terms (ADA Title II/III, DOJ deadlines, litigation) that are unlikely to fire for any other skill. Minimal conflict risk.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-ada-web-accessibility/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.