CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

74%

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

78%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 content is a lean, well-organized overview with concrete attribute-level review guidance and clean progressive disclosure to a single reference file. Its main weakness is mild redundancy between the Quick Reference and Check/Fix sections and the lack of an explicit re-verify feedback loop.

DimensionReasoningScore

Conciseness

The body is short, well-sectioned, and avoids re-teaching ARIA basics, but the opening motivation sentence and overlap between Quick Reference and the Check/Fix sections are minor tokens that could be trimmed.

4 / 5

Actionability

Gives concrete, attribute-level guidance (aria-label='Pagination', aria-current='page', focusable controls) and tells reviewers exactly what to flag; inline executable code is deferred to the reference, which is appropriate for a review skill.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections form a clear review workflow with the Check section acting as the verification checkpoint, though it is a section layout rather than an explicitly numbered sequence with a re-verify loop.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md') for full implementation details, code examples, and framework-specific guidance; the referenced file exists.

5 / 5

Total

17

/

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.

The description clearly states both what the skill does and when to use it, with a dedicated pagination-accessibility niche. It is slightly weakened by generic action verbs (review/validate) and broad triggers that could overlap with sibling HTML-review skills.

Suggestions

Replace generic verbs with more specific actions, e.g. 'Audit pagination markup for ARIA labels, current-page indication, and keyboard navigability'.

Tighten the trigger clause to pagination-specific phrases ('pagination controls', 'page navigation', 'paginated content') to reduce overlap with general HTML-review skills.

Rephrase 'related to Make pagination accessible' into a natural sentence to avoid the awkward embedded rule name.

DimensionReasoningScore

Specificity

Names the domain (pagination accessibility) and two concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' — but the actions are generic (review/validate) and coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' ('Validate the final browser-facing markup, not just the source framework abstraction') and 'when' ('Use when reviewing templates, rendered HTML, or shared components'), but the 'what' is narrow and the phrasing 'related to Make pagination accessible' is awkward.

4 / 5

Trigger Term Quality

Includes natural trigger terms a user would say ('reviewing templates, rendered HTML, shared components', 'pagination') with an explicit 'Use when' clause, though it lacks synonyms and file extensions for full coverage.

4 / 5

Distinctiveness Conflict Risk

The pagination-accessibility niche is distinct, but the broad trigger 'reviewing templates, rendered HTML, or shared components' risks overlap with other frontend HTML accessibility review skills.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.