CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-query

Compose React Table v9 with TanStack Query for server filtering, sorting, pagination, and infinite data. Load for query-key table state, manual* processing boundaries, server rowCount, keepPreviousData, or avoiding duplicated query-result state.

66

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a concise, actionable composition guide with executable Wrong/Correct code pairs and a clean section structure. It could nudge actionability to fully runnable by defining `columns` and add an explicit verification step for server-fetch correctness.

Suggestions

Add a minimal `columns` definition in the Setup snippet so the example is fully copy-paste runnable.

Add an explicit verification checkpoint (e.g., confirm `rowCount` and `data.rows` arrive together, or that changing pagination refetches) to catch silent server-fetch misconfigurations.

DimensionReasoningScore

Conciseness

The body is lean: a one-line framing sentence, compact executable snippets, and tight one-sentence rationales under each mistake; it assumes Claude's knowledge and avoids explaining what the libraries are.

5 / 5

Actionability

It provides copy-paste-ready TSX for setup and each pattern with explicit Wrong/Correct pairs, but the setup snippet omits the `columns` definition, leaving one small gap for a fully runnable example.

4 / 5

Workflow Clarity

Patterns are clearly labeled and sequenced (Setup, Core Patterns, Common Mistakes with severity tags and sources), and Wrong/Correct pairs act as implicit checkpoints; however there are no explicit validate/verify steps for a server-fetch workflow that could silently misbehave.

4 / 5

Progressive Disclosure

The content is well-organized into clearly signaled sections (Setup, Core Patterns, Common Mistakes, API Discovery) with no nested file references and appropriately inlined code; for a self-contained skill under the simple-skill threshold this is exemplary structure.

5 / 5

Total

18

/

20

Passed

Description

76%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 is specific and clearly niche, naming concrete capabilities and recognizable trigger phrases tied to TanStack Query + React Table composition. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the 'when' somewhat implicit.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when composing React Table v9 with TanStack Query for server-side data') to make the activation context unambiguous.

Add a couple of plain-language synonyms or natural phrasings (e.g., 'server-side table data', 'remote pagination') so users who don't use the exact API terms still trigger it.

DimensionReasoningScore

Specificity

Lists several concrete capabilities (server filtering, sorting, pagination, infinite data) plus concrete API hooks (query-key table state, manual* boundaries, server rowCount, keepPreviousData), with minor coverage gaps around error handling or caching specifics.

4 / 5

Completeness

The 'what' is clearly stated and 'when' is implied via the 'Load for...' trigger clause, but there is no explicit 'Use when...' phrasing and the trigger guidance is implicit rather than a direct instruction.

4 / 5

Trigger Term Quality

Natural trigger phrases like 'server filtering, sorting, pagination' and 'avoiding duplicated query-result state' are present and would be said by a user, though it leans somewhat technical and lacks a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (TanStack Query + React Table v9 composition) with distinct technical triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

17

/

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.