Name: with-tanstack-query
Rating: 60 (1 reviews)
Author: TanStack

with-tanstack-query

Compose Svelte Query with Svelte Table manual filtering, sorting, and pagination using reactive query inputs, query-result data getters, server counts, and a single source of server-data truth.

Quality

71%

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/svelte-table/skills/with-tanstack-query/SKILL.md

Quality

Content

83%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 lean, executable, and tightly scoped with strong Wrong/Correct examples, but it offers an implied rather than explicitly sequenced workflow and lacks validation checkpoints for a server-fetch composition task.

Suggestions

Add a short ordered workflow (e.g. 1. decide server-owned stages, 2. put them in queryKey, 3. expose data/rowCount via getters, 4. verify reactivity with a page change) so the composition sequence is explicit.

Include a verification checkpoint such as 'Confirm the query refetches on pagination changes and that rowCount drives page navigation' to close the loop on the reactive server-fetch task.

Consider splitting the API Discovery file-inspection guidance into a small reference file so the overview stays purely actionable, lifting progressive_disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: a tight Setup block plus short Core Patterns and Common Mistakes sections, no preamble explaining what Svelte Query/Table are, and every line carries actionable signal.	5 / 5
Actionability	Fully executable copy-paste-ready Setup code plus paired Wrong/Correct snippets for each mistake covering the common reactive-query, manual-mode, and count cases.	5 / 5
Workflow Clarity	It opens with a sequencing hint ('Decide which row-processing stages the server owns before composing Query') and the patterns imply an order, but there is no explicit numbered sequence or validation checkpoint for the composition, which involves server fetches and state synchronization.	3 / 5
Progressive Disclosure	Well-organized single-file overview with clear section headers and inline source pointers; no bundle files exist so all detail lives in SKILL.md, which is appropriate for this size, with only minor room to split the API-discovery reference out.	4 / 5
	Total	17 / 20 Passed

Description

58%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 distinct, naming concrete composition actions and a clear server-data-ownership niche, but it lacks any explicit 'when to use' trigger guidance and leans on technical jargon over natural user phrasing.

Suggestions

Add a 'Use when...' clause stating when Claude should reach for this skill, e.g. 'Use when wiring Svelte Query into a Svelte Table with manual/server-side pagination, filtering, or sorting.'

Include natural user-facing trigger phrases (e.g. 'server-side pagination', 'Svelte Query + Svelte Table', 'reactive server table') alongside the technical terms.

Clarify the single concrete outcome ('a single source of server-data truth') earlier so the 'what' lands before the mechanism list.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'manual filtering, sorting, and pagination', 'reactive query inputs', 'query-result data getters', 'server counts' — with minor gaps in coverage relative to a fully comprehensive action list.	4 / 5
Completeness	The 'what' is clearly stated (composing Svelte Query with Svelte Table for server-side stages), but there is no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant technical terms (TanStack Query, Svelte Table, filtering/sorting/pagination) appear, but natural user-facing phrases and synonyms are thin and the language leans toward jargon over what a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The composition niche (Query + Table manual stages with a single server-data owner) is fairly specific and mostly distinct, with only minor overlap risk against adjacent TanStack Table skills.	4 / 5
	Total	14 / 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/svelte-table/skills/with-tanstack-query/SKILL.md
Commit: 9e523bc

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.