react-query-best-practices

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

68%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 skill body is an efficient, concrete rule set that assumes Claude's competence and embeds executable patterns, with clearly signaled references. Its main weakness is a thin Steps section lacking explicit validation/verification checkpoints.

Suggestions

Expand the Steps into a clearer workflow with an explicit verification checkpoint, e.g. 'After applying fixes, re-scan the scope to confirm no rule is violated and no query is left disabled or duplicated.'

Add one short copy-paste example of a correct key factory and enabled-guard to make the audit patterns immediately executable.

Split the long compound rules (e.g. the server-prefetch rule) into bulleted sub-points for scannability.

Dimension	Reasoning	Score
Conciseness	The body is dense and rule-focused, assumes Claude already knows React Query, and avoids explaining basics, but several rules are long compound sentences that could be tightened, fitting the "efficient; minor instances of over-explanation that could be trimmed" anchor.	4 / 5
Actionability	Concrete, executable patterns are embedded directly in the rules (e.g. "Boolean(id) && (options?.enabled ?? true)", key-factory placement under hooks/queries/utils/), giving mostly executable guidance with minor gaps and no full copy-paste audit example block.	4 / 5
Workflow Clarity	The three Steps are sequenced (read references, analyze scope against rules, apply or propose fixes) but "Analyze the specified scope against the rules" is high-level with no explicit validation or verification checkpoint, matching the anchor with sequence present but checkpoints implicit.	3 / 5
Progressive Disclosure	Content is well-organized into Context, References, Rules, and Steps with clearly signaled one-level-deep external references; no bundle files exist, and the structure is good with only minor organization gaps in the dense inline rules.	4 / 5
	Total	15 / 20 Passed

Description

66%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 rich in domain keywords but omits any explicit "Use when..." trigger guidance, which caps completeness at 3. Voice is correctly third-person imperative and the niche is clearly distinguishable.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing React Query/TanStack Query usage, debugging stale data, or auditing server-state ownership.'

Include the 'TanStack Query' synonym so the description matches the natural phrasing more users say.

Lead with more than one action verb (e.g. 'Audit and fix React Query usage') to broaden the specificity of actions beyond a single verb.

Dimension	Reasoning	Score
Specificity	Names the domain (React Query best practices) and lists several concrete areas to audit — "key factories, staleTime, mutations, and server state ownership" — with the single action verb "Audit"; coverage is broad but rests on one verb rather than multiple distinct actions, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	It clearly answers "what" (audit React Query usage for best practices) but provides no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural keywords a React Query user would say ("React Query", "staleTime", "mutations", "key factories") but missing the common "TanStack Query" synonym and broader phrasings, fitting the "good keyword coverage; a few natural terms missing" anchor.	4 / 5
Distinctiveness Conflict Risk	The React Query niche with named sub-topics is mostly distinct with minimal conflict risk, though it could overlap with general code-review skills and lacks an explicit trigger clause, keeping it just below the clearly-distinct 5 anchor.	4 / 5
	Total	15 / 20 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: 7945b29

Reviewed: 3 days 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.