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

84%

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

76%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 well-structured and highly actionable with executable examples and a clean reference pointer, but it lacks explicit multi-step workflows with validation checkpoints for migration/server-state operations, and some detailed patterns are inlined rather than pushed to references.

Suggestions

Add a short sequenced workflow with validation checkpoints for at least one risky flow (e.g. migrating legacy Redux to RTK: set up store -> port slice -> run app -> verify reducers), so workflow_clarity can rise above 3.

Move the legacy Redux-to-RTK migration example into references/details.md alongside the other patterns, keeping SKILL.md as a lean overview to improve both conciseness and progressive disclosure.

Expand trigger/synonym coverage in the description (e.g. 'store', 'client state', 'caching') and consider splitting details.md into focused reference files (e.g. per-library) for clearer one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean tables, a concise Quick Start, and a Best Practices list, but the Quick Start Zustand example plus the inlined legacy-to-RTK migration example could be trimmed or deferred to references, so a couple of tokens do not fully earn their place.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript for a Zustand store and a RTK migration, plus a concrete selection-criteria decision table covering the common cases.	5 / 5
Workflow Clarity	Selection guidance and code patterns are present, but there is no sequenced multi-step workflow with validation/checkpoints for operations like migrations or optimistic updates; this skill involves batch/state operations where feedback loops would matter, so it caps at 3.	3 / 5
Progressive Disclosure	The body is a clear overview with well-organized sections and a clearly signaled one-level-deep pointer to references/details.md, but only one reference file exists and a couple of detailed patterns (e.g. the legacy Redux migration) are inlined rather than split out, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what the skill does and when to use it, naming concrete libraries and trigger conditions. The only minor gap is slightly less comprehensive natural-language synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the full domain (Redux Toolkit, Zustand, Jotai, React Query) and multiple concrete capabilities ('setting up global state, managing server state, choosing between state management solutions'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers what ('Master modern React state management with ...') and when ('Use when setting up global state, managing server state, or choosing between state management solutions') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users say ('global state', 'server state', 'choosing between state management solutions') plus named libraries, but misses common synonyms/variations like 'store', 'client state', or file/extension cues, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (React state management with named libraries) and distinct triggers, so it is unlikely to fire for unrelated skills and has minimal overlap risk.	5 / 5
	Total	19 / 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: wshobson/agents
Path: plugins/frontend-mobile-development/skills/react-state-management/SKILL.md
Commit: d6837ae

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