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.
74
66%
Does it follow best practices?
Impact
81%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/frontend-mobile-development/skills/react-state-management/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with excellent trigger terms and completeness, clearly identifying both what the skill covers and when to use it. The main weakness is that the capability description leans on library names rather than specific actions (e.g., 'configure stores', 'set up queries', 'migrate between solutions'). The use of 'Master' as the opening verb is slightly informal but still third-person.
Suggestions
Replace 'Master modern React state management' with specific concrete actions like 'Configure Redux Toolkit stores and slices, set up Zustand stores, implement Jotai atoms, and configure React Query for server state caching.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React state management) and lists specific libraries (Redux Toolkit, Zustand, Jotai, React Query), but doesn't describe concrete actions beyond 'setting up' and 'managing'. Missing specific actions like 'configure stores', 'create slices', 'implement caching strategies', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (React state management with specific libraries) and 'when' (explicit 'Use when setting up global state, managing server state, or choosing between state management solutions'). The 'Use when...' clause provides clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Redux Toolkit', 'Zustand', 'Jotai', 'React Query', 'global state', 'server state', 'state management'. These are terms developers naturally use when seeking help with React state management. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific library names (Redux Toolkit, Zustand, Jotai, React Query) and the focused niche of React state management. Unlikely to conflict with general React skills or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent, executable code examples across all major React state management libraries, making it highly actionable. However, it is far too verbose for a SKILL.md file—it reads more like a comprehensive tutorial than a concise skill reference. The content desperately needs progressive disclosure, splitting detailed patterns into separate files and keeping only a quick-start overview and decision guide in the main file.
Suggestions
Extract each pattern (Redux Toolkit, Zustand Slices, Jotai, React Query, Combined) into separate referenced files (e.g., REDUX_TOOLKIT.md, ZUSTAND.md) and keep only the selection criteria and one quick-start example in SKILL.md.
Remove the state categories table and best practices do's/don'ts—Claude already knows these concepts. Replace with a brief decision tree pointing to the appropriate pattern file.
Add a clear workflow for the common task of 'setting up state management in a new project' with explicit steps: assess needs → pick solution → implement → verify renders/performance.
Trim the migration guide to just a link to a separate MIGRATION.md file, or reduce it to a 3-line summary with a reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive code examples covering 5 different libraries. The state categories table, selection criteria, and concepts like 'colocate state' and 'normalize data' are things Claude already knows well. Much of this could be condensed significantly or split into separate reference files. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, type definitions, and realistic usage patterns. The Redux Toolkit, Zustand, Jotai, and React Query examples are copy-paste ready with complete implementations. | 3 / 3 |
Workflow Clarity | The selection criteria provide a basic decision flow, and the migration guide shows before/after, but there are no explicit validation checkpoints or step-by-step workflows for setting up state management. The 'When to Use' section lists scenarios but doesn't sequence them into a decision process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with all five patterns fully inlined. The Redux Toolkit pattern alone spans ~80 lines. Each pattern (Zustand slices, Jotai, React Query, combined pattern) and the migration guide should be in separate referenced files, with SKILL.md serving as a concise overview with links. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
91fe43e
- Reviewed
Table of Contents
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.