Name: pagination
Rating: 64 (1 reviews)
Author: TanStack

pagination

Paginate with rowPaginationFeature and paginatedRowModel or manualPagination. Load for pageIndex/pageSize state, rowCount/pageCount, unknown next-page limits, already-paginated server data, or autoResetPageIndex surprises.

Quality

77%

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 ./packages/table-core/skills/pagination/SKILL.md

Quality

Content

76%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-organized reference with concrete wrong/correct code pairs and no padding. The chief weakness is the absence of explicit validation/verification checkpoints in the workflow, which caps workflow clarity at 3.

Suggestions

Add an explicit verification step (e.g. assert pageCount/rowCount are set before rendering) so the workflow has a concrete checkpoint.

Replace fragmentary snippets like the lone `serverOptions` object with a minimal complete integration example so guidance is fully copy-paste ready.

Surface a short decision rule for choosing client slicing vs server pages up front, since the intro warns against mixing them but the body does not show how to decide.

Dimension	Reasoning	Score
Conciseness	The ~60-line body assumes Claude's competence throughout—never explaining what pagination is—and every section (Setup, Core Patterns, Common Mistakes, API Discovery) earns its tokens, matching 'lean and efficient; every token earns its place'.	5 / 5
Actionability	Provides executable TS with complete setup and wrong/correct pairs covering common cases, but some snippets are fragments (e.g. the lone `serverOptions` object) rather than fully copy-paste integrated examples, so it sits below the fully executable 5.	4 / 5
Workflow Clarity	A logical Setup→Patterns→Mistakes→Discovery sequence exists, but there are no explicit validation or verification checkpoints; the destructive/batch cap does not apply, yet checkpoints remain absent, matching 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and a one-level 'API Discovery' pointer to a real node_modules path; the body is just over 50 lines and has no bundle files to split, so it sits at 'good structure; minor organization gaps' rather than the simple-skill 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific, well-targeted description that names concrete APIs and trigger scenarios for TanStack table pagination. Its main gap is the absence of an explicit 'Use when' trigger clause, which caps completeness at 4.

Dimension	Reasoning	Score
Specificity	Names concrete APIs ('rowPaginationFeature', 'paginatedRowModel', 'manualPagination') and several specific scenarios (pageIndex/pageSize state, rowCount/pageCount, unknown next-page limits), landing at 'lists several specific actions; minor gaps' rather than the fully comprehensive 5.	4 / 5
Completeness	Both 'what' (Paginate with …) and 'when' (Load for … state, … limits, … server data, … surprises) are present, but the 'when' lacks an explicit 'Use when' framing, matching 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	Natural terms a TanStack-table user would say ('Paginate', 'pagination', 'pageSize', 'rowCount/pageCount') are present with good coverage, but a few synonyms (e.g. 'page navigation', 'next page') are missing, so it sits below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to TanStack table-core pagination with named features, giving a clear niche with minimal conflict risk, matching the top anchor.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: TanStack/table
Path: packages/table-core/skills/pagination/SKILL.md
Commit: d01c01b

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.