tanstack-query-expert

Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.

Quality

68%

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 ./skills/tanstack-query-expert/SKILL.md

Quality

Content

67%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable skill with excellent, production-ready code examples covering the most important TanStack Query patterns. Its main weaknesses are verbosity in explanatory prose (explaining concepts Claude already knows like what async state management is) and a monolithic structure that would benefit from splitting advanced topics into separate referenced files. The workflow sequences for optimistic updates and SSR hydration are well-structured but could include explicit verification steps.

Suggestions

Remove the 'Why TanStack Query?' section and the introductory paragraph — Claude already knows what TanStack Query does. Replace with a one-line summary if needed.

Split advanced topics (Optimistic Updates, Next.js SSR Integration, Query Key Factories) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.

Trim inline commentary in code examples (e.g., '// Cancel any outgoing refetches so they don't overwrite our optimistic update' can be shortened to '// Cancel outgoing refetches').

Dimension	Reasoning	Score
Conciseness	The skill contains several unnecessary explanations Claude already knows (e.g., 'TanStack Query is not just for fetching data; it's an asynchronous state manager', explaining what caching and deduplication are, the 'Why TanStack Query?' section). The opening paragraph restates the description. However, the code examples themselves are lean and well-targeted. There's room to trim explanatory prose while keeping the actionable content.	3 / 5
Actionability	Every major pattern is backed by complete, executable TypeScript code examples covering custom hooks, mutations with cache invalidation, optimistic updates with rollback, Next.js provider setup, and server-side hydration. The code is copy-paste ready with proper imports, types, and error handling.	5 / 5
Workflow Clarity	The optimistic update pattern has a clearly numbered 3-step sequence (onMutate → onError → onSettled) with explicit rollback logic. The Next.js SSR hydration flow is clearly sequenced across server and client components. However, there are no explicit validation checkpoints or verification steps (e.g., confirming the cache state after invalidation, or verifying hydration succeeded). Since these aren't destructive/batch operations, the missing validation doesn't cap the score at 3.	4 / 5
Progressive Disclosure	The content is a monolithic ~200-line file with no references to external files or bundle structure. The advanced patterns (optimistic updates, SSR hydration, query key factories) could be split into separate reference files. All content is inlined with section headers but no navigation strategy for a skill of this complexity.	2 / 5
	Total	14 / 20 Passed

Description

70%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 does a good job identifying the specific library (TanStack Query / React Query) and listing concrete capabilities, making it distinctive and reasonably specific. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The opening phrase 'Expert in' is slightly informal but uses third person appropriately.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about TanStack Query, React Query, data fetching with caching, or managing server state in React/Next.js applications.'

Include additional natural trigger terms users might say, such as 'useQuery', 'useMutation', 'cache invalidation', 'refetching', 'server state', or 'query keys'.

Dimension	Reasoning	Score
Specificity	Lists several specific capabilities: data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router SSR integration. These are concrete actions/topics, though some could be more granular (e.g., 'cache invalidation', 'query keys', 'infinite queries').	4 / 5
Completeness	The 'what' is clearly covered with specific capabilities, but there is no explicit 'when' clause (e.g., 'Use when...'). The absence of a 'Use when' clause caps this at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes strong trigger terms like 'TanStack Query', 'React Query', 'mutations', 'optimistic updates', 'stale time', 'SSR', and 'Next.js App Router'. Missing some natural user phrases like 'caching', 'refetching', 'useQuery', 'useMutation', or 'server state'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive — TanStack Query / React Query is a specific library with a clear niche. The mention of specific concepts like 'stale time configuration', 'optimistic updates', and 'Next.js App Router SSR integration' makes it very unlikely to conflict with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/tanstack-query-expert/SKILL.md
Commit: 3b73fbb

Reviewed: ~16 hours 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.