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.
77
66%
Does it follow best practices?
Impact
94%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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 acceptable as third person imperative.
Suggestions
Replace 'Master modern React state management' with specific concrete actions like 'Configure Redux Toolkit stores, set up Zustand/Jotai atoms, implement React Query caching, and migrate between state management solutions.'
| 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 multiple state management libraries, but is far too verbose for a SKILL.md — it reads more like a tutorial or documentation page than a concise skill file. It explains concepts Claude already knows (state categories, basic best practices), inlines ~250 lines of code that should be split into referenced files, and lacks workflow guidance for actually implementing these patterns in a project.
Suggestions
Reduce the SKILL.md to a concise overview with the selection criteria and one quick-start example (Zustand), then move Redux Toolkit, Jotai, React Query, and migration patterns into separate referenced files (e.g., REDUX_TOOLKIT.md, JOTAI.md, REACT_QUERY.md).
Remove the 'Core Concepts' state categories table and the Do's/Don'ts section — Claude already knows these fundamentals and they consume significant tokens.
Add a workflow section with explicit steps for setting up state management in a new or existing project, including validation checkpoints (e.g., 'verify store is accessible in components', 'confirm devtools connection').
Remove the 'When to Use This Skill' section — this is metadata that belongs in frontmatter, not in the body content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It explains state categories Claude already knows, includes a selection criteria table that's common knowledge, provides extensive boilerplate code for 5 different patterns, and includes a Do's/Don'ts section with generic advice like 'type everything' and 'don't mutate directly' that Claude inherently knows. The 'When to Use This Skill' and 'Core Concepts' sections add significant padding. | 1 / 3 |
Actionability | The code examples are fully executable, copy-paste ready TypeScript with proper imports, type definitions, and real-world patterns. The Redux Toolkit slice, Zustand store, Jotai atoms, and React Query hooks are all complete and immediately usable. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks workflow sequencing — there's no step-by-step process 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 migration guide shows before/after but not the migration process itself. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all 5 patterns fully inlined. There are no bundle files to offload detailed patterns to, and the content would benefit enormously from splitting Redux Toolkit, Zustand, Jotai, and React Query patterns into separate referenced files. External links at the bottom don't count as progressive disclosure of the skill's own content. | 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
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.