pagination

Use when auditing paginated content (blog archives, product category pages, search results). Applies to any site with lists or grids of content split across multiple pages.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pagination/SKILL.md

Quality

Content

65%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 with a clean overview-to-reference split and largely actionable, concrete audit and fix guidance. Its main weaknesses are redundancy between the 'Check' and 'Code Review' sections, an 'Explain' section covering familiar SEO concepts, and the absence of a post-fix verification step for what is effectively a batch change.

Suggestions

Merge the 'Code Review' section into 'Check' — they cover the same checks (self-canonicalization, URL-pattern consistency, infinite-scroll crawlability) with slightly different wording.

Add a re-verification step after the Fix guidance, e.g. 'After updating, re-crawl each paginated URL and confirm the canonical now self-references', to close the batch-operation feedback loop.

Trim the 'Explain' section's restatement of what canonical tags tell Google, keeping only the non-obvious consequence (content on later pages becomes unreachable from search).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the 'Explain' section reiterates what canonical tags tell Google (knowledge Claude already has) and 'Code Review' substantially duplicates the 'Check' section (canonical-to-page-1 flag, URL-pattern consistency, infinite-scroll crawlability). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 2, since there is no heavy padding and the 2019 rel=prev/next note is a legitimately non-obvious deprecated-pattern warning.	3 / 5
Actionability	Guidance is concrete and executable: specific URL patterns ("?page=, /page/, /p/, or numbered suffixes"), a precise verification rule ("page 2 canonical-url = page 2 URL"), and a copy-paste-ready fix example (<link rel='canonical' href='https://example.com/category?page=2' />). Minor gaps — no command for fetching/inspecting a page's canonical tag — keep it below level 5.	4 / 5
Workflow Clarity	The Check→Fix→Explain sequence is present, but the parallel 'Code Review' section repeats the check steps and muddies which procedure to follow, and there is no re-verification step after applying fixes. Since fixing canonical tags across a paginated sequence is a batch operation, the missing validate-after-fix feedback loop caps this at 3 per the rubric's scoring notes.	3 / 5
Progressive Disclosure	A ~46-line well-sectioned overview (Quick Reference, Check, Fix, Explain) with a single, clearly signaled, one-level-deep reference — references/rule.md, verified to exist — for 'full implementation details, code examples, and framework-specific guidance'. This matches the clear-overview-with-well-signaled-references anchor.	5 / 5
	Total	15 / 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 a clear, explicit trigger with well-chosen example contexts and a distinct niche, but it under-specifies what the skill actually does (auditing canonical tags on paginated pages) and omits the key term "pagination". It is solid but sits below the best-in-class examples.

Suggestions

State the concrete capability in the what-clause, e.g. 'Checks and fixes canonical tags on paginated pages (page 2, page 3...)' so the audit target is explicit.

Add the natural trigger term 'pagination' and related phrases like 'canonical tags', 'rel=canonical', and 'page 2' that users would say when needing this skill.

Trim the broad tail ('Applies to any site with lists or grids of content split across multiple pages') which inflates overlap risk with general canonical/duplicate-content skills.

Dimension	Reasoning	Score
Specificity	The description names the domain with concrete contexts ("blog archives, product category pages, search results") but offers only one generic action ("auditing") without saying what is actually checked, such as canonical tags. It matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than level 4, which requires several specific actions.	3 / 5
Completeness	Both halves are present: an explicit trigger ("Use when auditing paginated content...") and a what-statement ("Applies to any site with lists or grids of content split across multiple pages"). The 'when' is explicit but the 'what' stays vague about the actual capability (canonical-tag auditing), so it falls short of level 5's fully concrete what-and-when.	4 / 5
Trigger Term Quality	Natural phrases like "paginated content", "blog archives", and "search results" are present, but the most common trigger term — "pagination" itself — is absent, along with "canonical" and "rel=canonical". This fits 'some relevant keywords but missing common variations or synonyms' rather than level 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	Pagination auditing is a distinct niche with specific examples, mostly distinguishable from generic duplicate-content or canonical skills. However, "Applies to any site with lists or grids" keeps some overlap risk with a broader canonical-url skill, preventing a 5.	4 / 5
	Total	14 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/pagination/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.