CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

73%

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

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.

A lean, well-structured audit skill with concrete detection patterns and a copy-paste fix example, plus a properly signaled one-level reference to a real bundle file. Its weaknesses are the duplicated Check/Code Review sections, the Explain section re-teaching canonical basics Claude already knows, and the absence of any verify-after-fix step for a batch audit. Merging the two check sections and adding a brief validation step would lift both conciseness and workflow clarity.

Suggestions

Merge the 'Check' and 'Code Review' sections into one procedure — they cover the same detection steps (?page=, /page/, /p/ patterns, flagging canonicals pointing to page 1) and the duplication costs tokens and blurs the workflow.

Trim the 'Explain' section to one line or fold it into the fix rationale — the mechanics of what canonical tags tell Google is background Claude already knows.

Add a short verification step to the workflow (e.g., 'After updating, re-fetch the page and confirm the canonical equals the page's own URL'), which the batch nature of auditing many paginated pages warrants.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the 'Explain' section re-teaches canonical-tag semantics Claude already knows ('Pagination canonical tags tell Google which URL is the preferred version of each page'), and the 'Check' and 'Code Review' sections substantially duplicate each other (both describe finding ?page=, /page/, /p/ patterns and flagging canonicals pointing to page 1). This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, since the duplication is more than a minor trim.

3 / 5

Actionability

Concrete, executable guidance throughout: specific URL patterns to detect ('?page=, /page/, /p/, or numbered suffixes'), a copy-paste fix snippet ('<link rel=canonical href=https://example.com/category?page=2 />'), and explicit flag criteria. Minor gaps (e.g., where the canonical lives — HTML head vs. HTTP header — and no wrong-example HTML in the body) keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The Quick Reference → Check → Fix → Explain sequence is present, but the Check/Code Review redundancy creates ambiguity about which procedure to follow, and there is no verification step (e.g., re-checking that the updated canonical self-references) for what is a batch audit across many paginated pages. Per the rubric's cap for batch operations without validation, this caps at 3 even though the single-purpose flow is otherwise clear.

3 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a single, clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that points to a real file in the bundle. This matches the simple-skill exception: clear overview with well-organized sections and an appropriate external reference.

5 / 5

Total

15

/

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 solid description with an explicit 'Use when' trigger clause and concrete, natural trigger contexts. Its main weakness is that it never names the actual capability — checking/fixing canonical tags on paginated pages — so the 'what' is vague and keywords like 'canonical', 'SEO', and 'pagination' are absent. Adding one sentence naming the canonical-tag audit action would raise specificity, completeness, and trigger quality simultaneously.

DimensionReasoningScore

Specificity

The description names the domain and one action ('auditing paginated content') with concrete contexts ('blog archives, product category pages, search results'), but never states what aspect is audited (canonical tags). This sits between anchor 2 (minimal/generic actions) and anchor 3 (1-2 concrete actions); the concrete context examples pull it up to 3, while the absence of what is actually checked keeps it below 4.

3 / 5

Completeness

Both parts are present: an explicit 'Use when auditing paginated content' trigger clause with concrete contexts (the 'when'), and 'auditing paginated content' as the 'what'. The 'what' is vaguer than anchor 5 requires — it never says the audit checks canonical tags on paginated pages — matching anchor 4 ('both what and when; when could be more explicit or specific') rather than 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'paginated content', 'blog archives', 'product category pages', 'search results', 'lists or grids of content split across multiple pages'. However, common variations users would say are missing — notably 'canonical', 'pagination', and 'SEO' — so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The pagination niche ('paginated content', 'blog archives', 'product category pages', 'search results') is mostly distinct with clear triggers. Because 'canonical' is never mentioned, there is minor overlap risk with a closely related general canonical-tag or SEO-audit skill, matching anchor 4 rather than 5's 'clear niche with distinct triggers'.

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.

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