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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A well-structured, highly actionable reference with strong progressive disclosure and executable code, weakened only by some introductory fluff and the absence of explicit validation checkpoints in its workflows. The deeper patterns are correctly offloaded to a real one-level reference file.

Suggestions

Drop the introductory sentence 'Comprehensive guide to modern React state management patterns...' and tighten the State Categories table to the solution mapping only, since Claude already knows what local/global/server state categories are.

Add an explicit, sequenced workflow with a validation checkpoint for at least one multi-step task — e.g., a 'migrate legacy Redux to RTK' checklist with a compile/type-check or test-run verification step before declaring success.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (tables, concise code, short bullet lists), but it opens with restated-concept fluff ('Comprehensive guide to modern React state management patterns, from local component state to global stores and server state synchronization.') and the State Categories table partly explains concepts Claude already knows, so not every token earns its place.	2 / 3
Actionability	It provides fully executable, copy-paste-ready TypeScript — a complete Zustand store with middleware, typed hooks, and component usage, plus a before/after Redux Toolkit migration with createSlice.	3 / 3
Workflow Clarity	Content is organized and the Selection Criteria give a decision sequence, but there is no explicitly sequenced multi-step workflow with validation checkpoints; the migration is presented as before/after without feedback or verification steps.	2 / 3
Progressive Disclosure	SKILL.md is a clear overview with a well-signaled, one-level-deep pointer to references/details.md ('Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.'), and that reference file exists with the deeper patterns appropriately split out.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 concise, well-targeted description that clearly states both capability and explicit trigger conditions, with strong natural trigger terms and low conflict risk. Its only weakness is the vague 'Master' verb in place of concrete, enumerable actions.

Dimension	Reasoning	Score
Specificity	The opening verb 'Master' is a vague over-claim, and the concrete actions ('setting up global state, managing server state, or choosing between state management solutions') live only in the trigger clause and remain high-level rather than enumerating multiple specific concrete actions.	2 / 3
Completeness	It explicitly answers both 'what' ('Master modern React state management with...') and 'when' via an explicit 'Use when setting up global state, managing server state, or choosing between state management solutions.' clause.	3 / 3
Trigger Term Quality	Natural terms a developer would actually say are well covered — 'global state', 'server state', 'Redux Toolkit', 'Zustand', 'Jotai', and 'React Query'.	3 / 3
Distinctiveness Conflict Risk	The React state-management niche is clear and the triggers (global state, server state, choosing state solutions) are specific enough to avoid triggering unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 5cc2549

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.