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 imperative 'Master' at the start is slightly unusual but doesn't violate the third-person guideline as severely as first/second person would.
Suggestions
Replace 'Master modern React state management' with specific concrete actions like 'Configures Redux Toolkit stores, sets up Zustand/Jotai atoms, implements React Query caching' to improve specificity.
| 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.
This skill is essentially a comprehensive tutorial/reference document rather than a focused skill file. While the code examples are high-quality and executable, the content is far too verbose for a SKILL.md — it tries to cover 5 different state management libraries in full detail inline, explains concepts Claude already knows (state categories, best practices), and lacks any progressive disclosure structure. It would benefit enormously from being split into a concise overview with references to separate pattern files.
Suggestions
Reduce the main SKILL.md to a concise overview (~50-80 lines) with the selection criteria table and one quick-start example (Zustand), then move each library pattern into separate bundle files (e.g., patterns/redux-toolkit.md, patterns/zustand.md, patterns/jotai.md, patterns/react-query.md).
Remove the 'Core Concepts' state categories table and best practices do's/don'ts — Claude already knows these React fundamentals. Focus only on the specific, non-obvious guidance.
Add a decision workflow with explicit checkpoints: e.g., 'Step 1: Identify state type → Step 2: Check app complexity → Step 3: Implement chosen solution → Step 4: Verify re-render behavior with React DevTools'.
Remove the external resource links at the bottom — Claude already knows where these docs are — and replace with references to bundle files containing the detailed patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. The state categories table, selection criteria, best practices do's/don'ts, and migration guides all explain concepts Claude already knows well. The 'Core Concepts' section is essentially a tutorial overview that adds little actionable value. Multiple full-length code examples for 5 different libraries bloat the token budget significantly. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, type definitions, and realistic usage patterns. The Redux Toolkit slice, Zustand store, Jotai atoms, and React Query hooks are all copy-paste ready with complete implementations. | 3 / 3 |
Workflow Clarity | The selection criteria provide a basic decision flow, and patterns are clearly labeled and sequenced from simple to complex. However, there are no validation checkpoints, no debugging steps when things go wrong, and no explicit workflow for choosing and implementing a solution end-to-end. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no bundle files to offload detailed patterns. All five library patterns are fully inlined when they should be split into separate reference files. The external links at the bottom are to third-party docs, not to organized bundle files that could contain the detailed code examples. | 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
3974caa
- 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.