CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

accesslint-scan

Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally lean, actionable skill body with executable commands, a precise report format, and validation/feedback checkpoints throughout. Its only weakness is minor trimmable filler: the verbatim 'When to Use' duplication and boilerplate 'Limitations' text.

Suggestions

Drop or shrink the 'When to Use' section, which restates the description verbatim and adds no new information.

Replace the generic 'Limitations' boilerplate with skill-specific limits (e.g., what the CLI cannot detect, browser/JS constraints).

DimensionReasoningScore

Conciseness

The body is dense and operational (commands, report format, gotchas), but the 'When to Use' section repeats the description verbatim and the 'Limitations' section is generic boilerplate ('Do not treat the output as a substitute for environment-specific validation...') — minor instances of over-explanation that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands: the port-extraction one-liner, 'npx -y @accesslint/cli@latest "<url>" --port "$PORT" --format json', the teardown command, concrete flags (--selector, --wait-for, --include-aaa, --disable), and a fully specified per-violation report format.

5 / 5

Workflow Clarity

A clear three-step sequence (Audit, Report, Tear down) with explicit validation and feedback loops: 'apply mechanical ones then re-run to verify', 'CLI exit 2 = bad URL or page never loaded; check the dev server', and the conditional teardown skip 'if ensure reported "managed":false'. The skill is read-only, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (none exist in references/, scripts/, or assets/), and its content is well organized into clearly labeled sections, which per the rubric guideline merits a 5.

5 / 5

Total

19

/

20

Passed

Description

75%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 highly specific, distinctive description that clearly states what the skill does, weakened only by the absence of an explicit 'Use when' clause and a couple of natural synonyms like 'a11y'. Adding trigger guidance would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to audit, check, or test a page for accessibility, WCAG compliance, or a11y issues.'

Add natural synonyms such as 'a11y', 'accessibility check', or 'screen reader' to broaden keyword coverage.

Consider naming the input explicitly ('given a URL') to sharpen the when-conditions.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Audit a live page', 'locate each WCAG violation precisely', 'return a selector-grounded fix worklist', 'without editing' — covering the full task lifecycle (audit, locate, deliverable, boundary) with no coverage gaps for its domain.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'without editing' describes a scope boundary, not when to invoke the skill — which caps completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Natural terms like 'accessibility issues', 'WCAG', 'audit', and 'live page' are present, but common variations users say such as 'a11y' or 'screen reader' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Live page', 'WCAG violation', and 'selector-grounded fix worklist' carve out a clear niche (live-page accessibility auditing) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/accesslint-scan/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.