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. Its main weakness is that the capability description leans more toward naming tools than describing concrete actions (e.g., 'Master modern React state management' is somewhat vague about what specific tasks it performs). The use of imperative 'Master' at the start is slightly unusual but not a person-voice violation.
Suggestions
Replace 'Master modern React state management' with specific concrete actions like 'Configure stores, create state slices, set up caching, and migrate between state management libraries in React applications'
| 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 is present and provides clear triggers. | 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 narrow focus on 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 file. It reads more like a tutorial or documentation page than a concise skill reference, explaining many concepts Claude already knows. The monolithic structure with no progressive disclosure means the entire ~300-line document loads into context even when only one pattern is needed.
Suggestions
Drastically reduce content to a concise overview with selection criteria and one quick-start example, moving each pattern (RTK, Zustand slices, Jotai, React Query, combined) to separate referenced files like PATTERNS_RTK.md, PATTERNS_ZUSTAND.md, etc.
Remove the state categories table, best practices do's/don'ts, and migration guide from the main file—these explain concepts Claude already knows well and can be referenced in separate files if needed.
Add a brief workflow section with explicit steps for 'setting up state management in a new project' including validation checkpoints (e.g., verify store is accessible, test a selector, confirm devtools connection).
Remove the external resource links at the bottom—Claude already knows where these libraries' docs are.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive code examples for multiple libraries that Claude already knows well. The state categories table, selection criteria, best practices do's/don'ts, and migration guides all explain concepts Claude is already deeply familiar with. Much of this could be condensed to a fraction of its size. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, type definitions, and usage patterns. The examples are copy-paste ready and cover real-world scenarios like optimistic updates, async thunks, and middleware configuration. | 3 / 3 |
Workflow Clarity | The selection criteria provide a basic decision flow, and patterns are clearly separated, but there's no explicit workflow for setting up state management in a project (e.g., step-by-step with validation checkpoints). The migration guide shows before/after but lacks a sequenced migration process with verification steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. All five patterns, migration guides, best practices, and resources are inlined in a single document. The content would benefit enormously from splitting patterns into separate files with a concise overview linking to them. | 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
05d40bb
- 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.