react-query-best-practices

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

Quality

73%

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

Quality

Content

80%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 content is concise, well-structured, and provides concrete checkable rules, but the fix workflow lacks any validation step despite applying batch edits, and no code patterns illustrate the prescribed shapes.

Suggestions

Add an explicit validation step after applying fixes, e.g. 'Run typecheck/tests and verify the app builds; only then report the changes', to lift workflow clarity above 3.

Include one short code block showing the prescribed key-factory shape (all/lists/details hierarchy) so the 'how' is copy-paste ready, not just the 'what'.

Add a brief 'report findings' step summarizing violations found and fixes applied, giving the audit a clear terminal checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude knows React Query, and never pads with basic concepts; every rule and parenthetical justification earns its place.	5 / 5
Actionability	Rules are concrete and checkable ('forward signal', 'onMutate save / onError rollback'), but there are no code examples showing the prescribed key-factory or optimistic-update shapes, leaving a minor gap.	4 / 5
Workflow Clarity	The three steps (read references, analyze, apply/propose fixes) are sequenced, but applying fixes (fix=true) is a batch operation with no validation/verification checkpoint, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The sub-50-line body has no bundle files and is well-organized into clear sections with clearly signaled one-level external references, satisfying the simple-skill exception.	5 / 5
	Total	17 / 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 distinctive, naming React Query and four concrete audit domains, but it omits any explicit 'Use when' trigger guidance, which caps completeness at 3. Adding a trigger clause would lift the score meaningfully.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing React Query usage, auditing server-state patterns, or debugging staleTime/invalidation issues.'

Include the 'TanStack Query' synonym in the description so users who say the rebranded name still trigger the skill.

Consider stating the audit output ('reports violations and optionally applies fixes') to sharpen the 'what does this do' half.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates four concrete audit areas ('key factories, staleTime, mutations, and server state ownership'), matching the 'lists several specific actions' anchor rather than the comprehensive multi-action level 5.	4 / 5
Completeness	It clearly states what the skill does ('Audit React Query usage for best practices') but has no 'Use when...' trigger clause, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	'React Query' plus concrete API concepts (staleTime, key factories, mutations) gives good domain keyword coverage, though it leans technical and omits natural synonyms like 'TanStack Query'.	4 / 5
Distinctiveness Conflict Risk	'React Query' is a named library with a clear best-practices-auditing niche and low conflict risk, though the absence of an explicit trigger phrase leaves minor overlap with general React/state skills.	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: 417ae20

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.