CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pagination-accessibility

Use when reviewing templates, rendered HTML, or shared components related to Make pagination accessible. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

72%

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

Quality

Content

70%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 well-structured as a simple review skill with a clear Check/Fix/Explain sequence and exemplary progressive disclosure — a lean overview deferring to a real, one-level-deep reference file. Its weaknesses are moderate redundancy (the same ARIA attributes repeated across three sections plus an unnecessary motivation line) and incomplete actionability, with no inline example markup and two Quick Reference bullets that name a goal without the mechanism to achieve it.

Suggestions

Add a short accessible-pagination HTML snippet to the Fix section so the fix is copy-paste ready rather than attribute-level description.

Make the vague Quick Reference bullets concrete: specify how to announce page changes (e.g., aria-live region or moving focus on route change) and what a 'clear label' for prev/next controls looks like (e.g., aria-label='Previous page').

Consolidate the repeated nav/aria-label/aria-current attribute lists across Quick Reference, Check, and Fix into a single source of truth, and drop the opening motivation sentence Claude does not need.

DimensionReasoningScore

Conciseness

The body is short but not tight: the opening motivation sentence ('Without proper markup, screen reader users cannot...') explains a concept Claude already knows, and the same attribute list (nav + aria-label, aria-current='page') is repeated nearly verbatim across Quick Reference, Check, and Fix. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is above anchor 2 because there is no library-tutorial-style padding, and below anchor 4 because the triplicated attribute lists and motivation line are clear trim candidates.

3 / 5

Actionability

About half the guidance is concrete and executable ("Use nav element with aria-label='Pagination'", "aria-current='page'", "nav role='navigation'", "focusable controls"), but key details are missing: there is no example markup anywhere in the body, and two Quick Reference bullets — "Provide clear labels for previous/next buttons" and "Announce page changes to screen readers" — give no mechanism (no aria-live guidance, no labeling example). This is anchor 3 ('some concrete guidance but incomplete... missing key details') rather than anchor 4, since the gaps go beyond minor.

3 / 5

Workflow Clarity

This is a simple, single-purpose review skill (45-line SKILL.md), and the Check → Fix → Explain → Code Review sections make the single action unambiguous: what to verify, what a compliant implementation contains, and what to flag during code review. Per the simple-skill exception, a clear, well-organized single-action skill scores 5; no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The SKILL.md body is a lean overview with well-organized sections, and it clearly signals exactly one one-level-deep reference — "see `references/rule.md`" — which is a real 346-line bundle file containing the implementation details and code examples. No nested references exist in rule.md, and nothing that belongs in a separate file is inlined, matching the simple-skill and clear-overview anchors.

5 / 5

Total

16

/

20

Passed

Description

62%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 has an explicit and well-formed 'Use when...' trigger clause and a clear, domain-specific directive about validating rendered markup rather than framework abstractions. Its weaknesses are a thin 'what' (only one validate action, no mention of what to check for) and missing common accessibility synonyms such as 'screen reader', 'a11y', or 'aria' that users naturally say.

Suggestions

State what is actually validated, e.g. 'Validate pagination markup: nav element with aria-label, aria-current on the active page, and keyboard-navigable controls' — this would raise both specificity and the completeness of the 'what' side.

Add natural trigger synonyms users say for this need, such as 'screen readers', 'a11y', or 'page navigation', to broaden trigger-term coverage.

Replace the boilerplate 'related to Make pagination accessible' phrasing with a smoother clause like 'related to accessible pagination', which reads more like natural user language.

DimensionReasoningScore

Specificity

The description names the domain ("pagination accessible" in "rendered HTML", "templates", "shared components") and one to two concrete actions ("Validate the final browser-facing markup"), but never states what is actually validated (nav element, aria-current, keyboard navigability). This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it is above anchor 2 because validating rendered markup vs. the source abstraction is a concrete, specific directive, and below anchor 4 because no several specific actions are listed.

3 / 5

Completeness

Both parts are present: the 'when' is an explicit "Use when reviewing templates, rendered HTML, or shared components related to Make pagination accessible" clause, and the 'what' is "Validate the final browser-facing markup, not just the source framework abstraction". Not anchor 5 because the 'what' is thin — it does not say what about the markup is validated or what the skill does beyond one validate action; the what-side lacks the concrete trigger-phrase richness of the anchor 5 example.

4 / 5

Trigger Term Quality

Relevant natural terms are present ("pagination", "accessible", "templates", "rendered HTML", "shared components", "markup"), but common synonyms and phrases users would naturally say for this need — "screen reader", "a11y", "WCAG", "aria", "page navigation" — are all missing. This fits anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than anchor 4, since the missing synonyms are ones users frequently use when requesting accessibility checks.

3 / 5

Distinctiveness Conflict Risk

The pagination-accessibility niche is specific and would rarely trigger for unrelated skills. However, the shared boilerplate pattern ("Use when reviewing templates, rendered HTML, or shared components related to...") is generic across sibling frontend-checklist skills, leaving minor overlap risk with closely related HTML accessibility rules — matching anchor 4 rather than anchor 5's 'clear niche with distinct triggers'.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/pagination-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.