CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

80%

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

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 compact, code-driven skill that wastes no tokens and gives concrete wrong-vs-correct guidance for common pagination pitfalls. It lacks validation/verification checkpoints, which caps workflow clarity, and its examples are occasionally fragments rather than fully copy-pasteable option objects.

Suggestions

Add a brief validation step for manual pagination (e.g., assert the provided page length matches pageSize and that rowCount/pageCount is set) to establish a feedback loop.

Turn the Wrong/Correct snippets into complete, copy-pasteable options objects (including data and the surrounding hook call) so the examples run as-is.

Make the 'API Discovery' pointer more explicit about which files/symbols to read (e.g., name the specific reset or count-calculation exports).

DimensionReasoningScore

Conciseness

Lean and efficient throughout: setup code, a one-line server pattern, and three terse Wrong/Correct mistake entries with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides executable TypeScript snippets (imports, features wiring, server options, Wrong/Correct options) but the manual-mode and reset examples are fragments rather than full copy-paste-ready option objects, leaving minor gaps.

4 / 5

Workflow Clarity

Sections are sequenced (Setup, Core Patterns, Common Mistakes, API Discovery) but there are no validation/checkpoint steps; per the destructive/batch cap, a skill showing wrong-vs-correct patterns without verification guidance cannot exceed 3.

3 / 5

Progressive Disclosure

Well-organized short sections with a clear 'API Discovery' pointer into node_modules for deeper inspection; no bundle files exist, so structure relies on in-body sections plus the one external pointer, with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

83%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 dense, technically precise description that names concrete APIs and several concrete load-conditions serving as triggers. It is strong on specificity and distinctiveness, though the trigger framing leans technical and lacks a clean user-voice 'Use when' phrasing.

Suggestions

Add an explicit 'Use when...' clause in user voice (e.g., 'Use when paginating rows, handling server-side pages, or fixing unexpected page resets').

Include common synonyms a user might say such as 'page number', 'page size', 'page count', and 'server-side pagination'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named APIs ('Paginate with rowPaginationFeature and paginatedRowModel or manualPagination') plus specific load conditions (pageIndex/pageSize state, rowCount/pageCount, unknown next-page limits, autoResetPageIndex surprises).

5 / 5

Completeness

Clear 'what' (paginate via the two mechanisms) and an explicit trigger clause ('Load for ... unknown next-page limits ... or autoResetPageIndex surprises'), but the 'when' is framed as load-conditions rather than a clean 'Use when...' user-facing trigger.

4 / 5

Trigger Term Quality

Strong natural terms (pagination, pageIndex, pageSize, rowCount, pageCount, manual pagination, next-page) but misses common user phrasings and synonyms like 'pages', 'page count', 'server-side pagination'; mostly technical vocabulary.

4 / 5

Distinctiveness Conflict Risk

Highly specific to TanStack table-core pagination with unique API names (rowPaginationFeature, paginatedRowModel, manualPagination); minimal risk of triggering for an unrelated skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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