accesslint-diff

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/agentic-awesome-skills-claude/skills/accesslint-diff/SKILL.md

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.

The body is a strong, executable runbook: concrete commands, a clear three-phase workflow with real validation and restore steps, and tight self-contained structure. Only minor conciseness and explicit-verification refinements would lift it further.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven and assumes Claude's competence, with only minor trim opportunities — the 'When to Use' section repeats the description verbatim and the 'Limitations' section is generic boilerplate.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags (`npx -y @accesslint/cli@latest "<url>" --port "$PORT" --snapshot ...`, `git stash push -u -m ...`) plus a concrete example report format cover the common cases.	5 / 5
Workflow Clarity	A clear numbered Audit → Report → Tear down sequence carries explicit validation checkpoints (`git check-ref-format --branch`, `case -*) ... exit 1`, `git rev-parse --verify`) and error-recovery gotchas, but working-tree restoration after `git stash pop` / `git switch -` is implicit rather than an explicit verify step.	4 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections and no bundle files; nothing inlined belongs in a separate file, and the absence of external references is appropriate rather than a navigation gap.	5 / 5
	Total	18 / 20 Passed

Description

67%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 excels at stating concrete capabilities and carving out a distinct niche, but it lacks an explicit 'when to use' trigger clause and natural synonym coverage, capping completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when you want to see which accessibility violations a code change introduced or fixed, rather than running a full audit.', to lift completeness above 3 and give Claude a clear activation signal.

Broaden trigger-term coverage with natural synonyms users actually say — 'a11y', 'WCAG', 'ADA', 'contrast', 'alt text' — alongside 'accessibility violations'.

Reframe mechanism terms ('stash-based', 'uncommitted changes') as supporting detail so the lead phrase reads as a user-facing trigger rather than an implementation note.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Diff a live page's accessibility violations against a baseline', 'compares uncommitted changes (stash-based)', 'pass --branch [<name>] to diff against a branch', and 'Reports only new violations introduced, violations fixed, and pre-existing count' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent trigger guidance — the only trigger-like phrase ('Use `scan` for a full audit with no diffing') redirects to a sibling skill rather than stating when to use this one, so completeness is capped at 3.	3 / 5
Trigger Term Quality	'accessibility violations' is a relevant natural keyword, but the other terms ('stash', 'baseline', 'uncommitted changes', 'branch') describe mechanism rather than what a user says when they need the skill, and common synonyms like 'a11y', 'WCAG', 'ADA', or 'contrast' are missing.	3 / 5
Distinctiveness Conflict Risk	The niche (diffing a live page's accessibility violations against a baseline) is crystal clear, and it is explicitly disambiguated from the sibling `scan`/audit skill, leaving minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: plugins/agentic-awesome-skills-claude/skills/accesslint-diff/SKILL.md
Commit: 7b534bc

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.