CtrlK
BlogDocsLog inGet started
Tessl Logo

accesslint-scan

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

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/accesslint-scan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, highly actionable audit skill with executable commands, a clear three-step workflow, and good error-handling guidance. The only slack is redundant 'When to Use'/'Limitations' boilerplate and a missing explicit validation checkpoint in the main flow.

Suggestions

Remove or compress the 'When to Use' section since it restates the description verbatim.

Add an explicit validation checkpoint after the audit command (e.g. 'confirm the JSON is valid before building the report').

Trim the generic 'Limitations' boilerplate to the one risk specific to this skill (auditing is read-only; fixes need re-verification).

DimensionReasoningScore

Conciseness

The core (Audit/Report/Tear down, Gotchas) is lean and assumes competence, but the 'When to Use' section duplicates the description verbatim and 'Limitations' is generic boilerplate that could be trimmed.

4 / 5

Actionability

Copy-paste-ready bash for launching the audit and tearing it down, plus concrete flags, a structured report schema (where/evidence/fix), and decoded exit codes — fully executable.

5 / 5

Workflow Clarity

Clear Audit→Report→Tear down sequence with a 're-run to verify' feedback loop and exit-2 error recovery, but the main flow lacks an explicit validate step between audit output and reporting.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized numbered sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific, distinctive accessibility-audit description with strong action verbs and natural trigger terms, weakened only by the absence of an explicit 'when to use' clause. Adding a concrete trigger sentence would lift completeness.

Suggestions

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

Add a natural synonym such as 'a11y' or 'accessibility scan' to broaden trigger-term coverage.

Optionally name the output format (e.g. 'JSON worklist') so the deliverable is unambiguous.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Audit a live page', 'locate each WCAG violation precisely', 'return a selector-grounded fix worklist') plus an explicit non-editing constraint, but coverage is tightly scoped rather than comprehensive.

4 / 5

Completeness

The 'what' is clearly stated (audit, locate, return worklist) but there is no explicit 'Use when…' trigger clause, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Includes natural phrases users say ('accessibility issues', 'WCAG violation', 'audit a live page', 'fix worklist') with good coverage, but lacks synonyms and common variants like 'a11y' or specific WCAG criteria.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (live-page accessibility auditing with selector-grounded output) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation15 / 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
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.