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 high-quality, executable code examples across multiple state management libraries, but suffers significantly from verbosity and poor progressive disclosure. It reads more like a comprehensive tutorial than a concise skill reference—most of these patterns are well-known to Claude and don't need full inline examples. The content would benefit enormously from being split into separate files with the main SKILL.md serving as a decision guide with brief snippets.
Suggestions
Split each pattern (Redux Toolkit, Zustand, Jotai, React Query) into separate reference files and keep only the selection criteria and a minimal quick-start example in SKILL.md
Remove or drastically condense the best practices section—these are standard React knowledge Claude already has
Add a decision workflow with explicit steps: 'Identify state type → Check selection criteria → Apply pattern → Verify with [specific test]'
Cut the state categories table and selection criteria to just the decision flowchart—Claude knows what local vs global vs server state means
| 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 best practices sections explain concepts Claude already knows well. Much of this could be condensed significantly—e.g., the full Redux Toolkit slice with async thunk pattern is standard boilerplate Claude can generate without instruction. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, type definitions, and realistic usage patterns. The examples are copy-paste ready and cover real-world scenarios like optimistic updates, middleware configuration, and slice composition. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks workflow sequencing—there are no step-by-step processes for setting up state management in a project, no validation checkpoints, and no guidance on how to verify the state management is working correctly. The 'When to Use' section lists scenarios but doesn't sequence decisions. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. All five patterns with full code examples are inlined, making this extremely long. The Redux Toolkit, Zustand slices, Jotai, React Query, and migration guide content should be split into separate reference files with the SKILL.md serving as an 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
34632bc
- 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.