react-state-management

Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.

Quality

75%

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 ./skills/react-state-management/SKILL.md

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 skill is highly actionable with complete, executable code across all major React state libraries. Its weaknesses are a generic, low-value Instructions section that dilutes conciseness and workflow clarity, and a monolithic structure that lacks progressive disclosure into bundle files.

Suggestions

Replace the generic 'Instructions' bullets with a concrete decision workflow (e.g. classify the state category from the table, match it to a solution via the selection criteria, then apply the matching pattern), and add a validation step for migrations (verify reducers/slices behave identically after migrating from legacy Redux).

Split the per-pattern deep dives (Redux Toolkit slice, Zustand slices, Jotai atoms, React Query) into separate reference files under references/ and link to them one level deep from SKILL.md, leaving the selection criteria and one quick-start example inline.

Remove the boilerplate 'Do not use this skill when' and generic 'Instructions' sections, or replace them with skill-specific guidance that adds information Claude does not already have.

Dimension	Reasoning	Score
Conciseness	The body is code-dense and mostly efficient, but the generic 'Instructions' bullets ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') add little value and could be trimmed.	4 / 5
Actionability	Five full copy-paste-ready TypeScript patterns plus a before/after migration example provide concrete executable guidance covering the common React state cases.	5 / 5
Workflow Clarity	As a pattern catalog the sequence is implicit, and the 'Instructions' section is generic with no explicit validation checkpoints for risky operations like state migrations.	3 / 5
Progressive Disclosure	The single ~440-line SKILL.md inlines per-pattern deep dives and the migration guide with no bundle files and no one-level-deep internal references; structure exists via headers but bulk content that could live in separate files is not split out.	3 / 5
	Total	15 / 20 Passed

Description

78%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, action-oriented, and clearly scoped to React state management with concrete trigger guidance. The main weakness is moderate generality in the 'when' clause, which keeps completeness and trigger quality at 4 rather than 5.

Suggestions

Tighten the 'Use when' clause with concrete trigger scenarios (e.g. 'Use when migrating from legacy Redux to RTK, adding server caching with React Query, or wiring optimistic updates').

Add natural user-facing synonyms to the trigger terms (e.g. 'Redux', 'state library', 'global store') so the description matches how users phrase the request.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete libraries plus actions ('setting up global state, managing server state, or choosing between state management solutions'), listing several specific actions with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (master React state management with the named tools) and 'when' ('Use when...'), but the 'when' clause stays somewhat general rather than enumerating concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes natural trigger phrases ('setting up global state', 'managing server state', 'choosing between state management solutions') with good keyword coverage, though a few common variations (e.g. 'Redux migration', 'state library') are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (React state management) with named libraries and distinct triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/react-state-management/SKILL.md
Commit: 3eff4af

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