CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-query-best-practices

Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/react-query-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 tight, project-specific enforcement checklist with concrete file paths, expressions, and helper names, and clean one-level-deep reference delegation. Its main weakness is the fix=true workflow, which applies batch edits with no validation or feedback loop.

Suggestions

Add a validation checkpoint to the fix=true path, e.g. "After applying fixes, run the typecheck/tests and review the diff; fix and re-verify on failure."

Include one before/after violation example (e.g., a component copying query data into useState) to anchor what a finding and its fix look like.

Split the long key-factory bullet into two or three shorter bullets so each rule is independently scannable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what React Query is and states only project-specific constraints ("Server data must never be duplicated into useState or Zustand outside of mutation callbacks"). It is not 5 because a few passages could be trimmed: the long run-on key-factory bullet and the parenthetical "(fires on success and error)" explain semantics Claude already knows.

4 / 5

Actionability

Guidance is highly concrete: exact paths (".claude/rules/sim-queries.md", "hooks/queries/utils/prefetch-query-on-intent.ts"), a copy-paste-ready expression ("Boolean(id) && (options?.enabled ?? true)"), and named helpers ("prefetchQueryOnIntent(queryClient, sharedQueryOptions)"). It is not 5 because there are no before/after violation examples or an expected output format for the audit findings — minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

The steps are clearly sequenced ("1. Read the references... 2. Analyze the specified scope... 3. If fix=true, apply the fixes") but the fix=true path is a batch edit operation with no validation checkpoint (no typecheck, test run, or diff review before finishing), which caps workflow clarity at 3 per the batch-operation rule. It is not 4 because validation is entirely absent rather than a minor gap.

3 / 5

Progressive Disclosure

The ~47-line body is well organized into Context, References, Rules, and Steps, and delegates detail one level deep to clearly annotated references ("https://tkdodo.eu/blog/effective-react-query-keys — key factory pattern, hierarchical keys, fuzzy invalidation") and to project rule files. No bundle files exist or are needed, so the under-50-line well-organized-sections standard for a 5 applies. It is not 4 because navigation is clean and nothing that belongs in a separate file is inlined.

5 / 5

Total

16

/

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.

The description is specific, concrete, and clearly niche-scoped to React Query auditing, with a strong enumeration of focus areas. Its main weakness is the complete absence of 'when to use' trigger guidance and of common synonyms like TanStack Query, which cap completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when auditing or reviewing code that uses React Query / TanStack Query (useQuery, useMutation, queryClient, query invalidation)."

Include the synonym "TanStack Query" and the hook names "useQuery" / "useMutation" so users who use those terms still match the skill.

DimensionReasoningScore

Specificity

"Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership" names the domain and enumerates four concrete focus areas. It sits at 4 rather than 5 because the coverage has minor gaps (e.g., query invalidation, error handling, DevTools) and enumerates topics under a single audit action rather than multiple distinct concrete actions.

4 / 5

Completeness

The 'what' is clear ("Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership") but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is missing outright rather than merely imprecise.

3 / 5

Trigger Term Quality

"React Query", "staleTime", "key factories", "mutations", and "server state" are terms users would naturally say. It falls short of the 5 anchor because common synonyms and hook names are missing — "TanStack Query", "useQuery", "useMutation", "query invalidation" — which are the phrases many users would actually use.

4 / 5

Distinctiveness Conflict Risk

"React Query" combined with library-exclusive concepts like "key factories" and "staleTime" carves a clear niche with distinct triggers and minimal conflict risk against other skills. It is not 4 because the trigger terms are specific to this one library rather than merely 'mostly distinct' with overlap risk against closely related skills.

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

simstudioai/sim

Path

.agents/skills/react-query-best-practices/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.