CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/tanstack-query-expert/SKILL.md

The canonical home for this skill is tanstack-query-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 strong, action-oriented skill body: executable, idiomatic TypeScript patterns with an excellent Do/Don't list and a concrete troubleshooting section. Its main costs are a conceptual "Why TanStack Query?" section that re-teaches library basics and a monolithic single-file layout where advanced SSR content could be split into references.

Suggestions

Delete or compress the "Why TanStack Query?" section — Claude already knows what the library does; keep only the "Rule of Thumb" line.

Define or stub the missing functions in examples (`updateTodoFn`, `fetchPostsServerSide`/`fetchPostsClientSide`) so every code block is fully copy-paste runnable.

Split the Next.js App Router SSR/hydration section into a references/ file, keeping a short inline summary with a clearly signaled link, to reduce SKILL.md body size.

DimensionReasoningScore

Conciseness

The body is mostly tight code-plus-one-line-framing, but the "Why TanStack Query?" section re-explains what the library does ("It handles caching, background updates, deduplication of multiple requests... out-of-the-box loading/error states") — knowledge Claude already has — and the intro paragraph pads with role-play phrasing ("You are a production-grade... expert. You master..."). This matches anchor 3: mostly efficient with some unnecessary explanation; not 4 because the conceptual section is a clear trim candidate, not a minor one.

3 / 5

Actionability

Nearly all guidance is executable, commented TypeScript: the custom-hook useQuery example, query key factory, mutation with invalidation, provider setup, and HydrationBoundary prefetch flow are copy-paste ready. Minor gaps keep it from anchor 5: the optimistic-update example references an undefined `updateTodoFn`, the Next.js example uses undefined `fetchPostsServerSide`/`fetchPostsClientSide`, and the mutation's `res.json()` lacks the `res.ok` check used elsewhere.

4 / 5

Workflow Clarity

The optimistic-updates section lays out an explicitly numbered sequence — cancel queries, snapshot, setQueryData, roll back in onError, always invalidate in onSettled — which is a genuine error-recovery feedback loop, and the Troubleshooting section maps concrete problems to fixes. Not anchor 5 because the skill is a pattern reference rather than a single end-to-end workflow, so there is no unified validate-before-proceed checklist across sections.

4 / 5

Progressive Disclosure

The single-file body is organized into clear, well-labeled sections (hook pattern, query keys, mutations, Next.js, best practices, troubleshooting) with nothing buried — matching anchor 4's good structure with minor gaps. Not anchor 5 because there are no well-signaled external references; the ~70-line Next.js SSR hydration section and the full optimistic-update implementation could live in reference files to slim the SKILL.md overview.

4 / 5

Total

15

/

20

Passed

Description

70%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 with good natural keywords and a clear niche, but it omits any explicit "Use when..." trigger guidance, capping its completeness. Adding a when-clause and a few more hook-level trigger terms would bring it to top tier.

Suggestions

Add an explicit when-clause, e.g., "Use when working with useQuery/useMutation hooks, configuring staleTime or cache invalidation, or hydrating queries in the Next.js App Router."

Include hook-level trigger terms users actually say — useQuery, useMutation, query keys, invalidateQueries, server state — to broaden natural-language matching.

Replace the role-claim framing ("Expert in...") with an action-verb lead ("Configure and implement...") for slightly more concrete capability statements.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration" — which goes beyond naming the domain. It falls short of anchor 5 because coverage has minor gaps (no mention of cache invalidation, query keys, or pagination) and the listed items are topic areas framed by the vague role-claim "Expert in TanStack Query" rather than pure action verbs.

4 / 5

Completeness

The "what" is clearly stated ("asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates..."), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the judging guidelines. It is not a 2 because the "what" is concrete and multi-part, and not a 4 because no "when" guidance exists even weakly.

3 / 5

Trigger Term Quality

Strong natural keyword coverage including both library names ("TanStack Query", "React Query"), "data fetching", "mutations", "optimistic updates", "stale time", and "Next.js App Router (SSR)". It is not anchor 5 because common user phrasings like "useQuery", "useMutation", "query keys", "invalidate the cache", and "server state" are absent.

4 / 5

Distinctiveness Conflict Risk

The description names a specific library (with its former name "React Query") and a distinct, well-bounded niche (async state management for React/Next.js), with trigger terms unlikely to fire for unrelated skills. This matches anchor 5's clear-niche pattern; only an extremely generic React state skill could overlap.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/tanstack-query-expert/SKILL.md

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.