react-query-best-practices

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

Quality

85%

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

Quality

Content

87%

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

An exceptionally concise, actionable, well-organized instruction skill whose only gap is the lack of a validation/feedback loop around the code-mutating fix step. Adding a verify-then-commit checkpoint would round it out.

Suggestions

Add an explicit validation checkpoint after applying fixes, e.g. 'After fixes, re-read each changed query to confirm the rule is satisfied before finalizing.'

For fix=true, include a brief error-recovery note (what to do if a fix breaks compilation or a queryFn signature) to form a validate→fix→retry loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and rule-driven with no padding or explanation of concepts Claude already knows; every line is a concrete, load-bearing rule. Not a 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Rules are concrete and specific ('forward signal', 'explicit staleTime from a named exported constant', 'onSettled not onSuccess', 'save previous data in onMutate, roll back in onError'). As an instruction-only skill the absence of code is not penalized, and the guidance is fully actionable. Not a 2 because no key details are missing.	3 / 3
Workflow Clarity	The three Steps are sequenced but applying fixes (fix=true default) is a code-mutating/batch operation with no validation checkpoints or error-recovery feedback loop, which the guidelines cap at 2. Not a 3 because there is no validate→fix→retry loop for the destructive fix step; not a 1 because the sequence is present and unambiguous.	2 / 3
Progressive Disclosure	A single, well-organized SKILL.md with clearly signaled one-level-deep references (three tkdodo.blog URLs) and no bundle files to misroute. Not a 2 because content is appropriately compact and references are clearly labeled rather than buried or nested.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 strong natural trigger terms and low conflict risk, weakened only by the absence of an explicit 'Use when...' clause. Adding trigger guidance would raise completeness to the top level.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when auditing or fixing React Query (TanStack Query) usage for best practices.'

Optionally add 'TanStack Query' alongside 'React Query' to capture the alternate naming users may say.

Dimension	Reasoning	Score
Specificity	Names multiple concrete audit targets — 'key factories, staleTime, mutations, and server state ownership' — matching the anchor for listing several specific concrete actions. It is not a 2 because it goes beyond naming only a domain and partial actions.	3 / 3
Completeness	It clearly states what the skill does ('Audit React Query usage for best practices') but lacks any explicit 'Use when...' or equivalent trigger guidance, which the guidelines cap at 2. It cannot be a 3 without an explicit when-clause.	2 / 3
Trigger Term Quality	Uses natural domain terms a developer would actually say ('React Query', 'staleTime', 'mutations', 'key factories') with good coverage of common variations. Not a 2 because the keyword set is comprehensive rather than partial.	3 / 3
Distinctiveness Conflict Risk	The niche is clear (React Query best-practices auditing) with distinct triggers unlikely to overlap with unrelated skills. Not a 2 because the scope is too specific to generically conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 6f514c1

Reviewed: about 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.