zustand-state-management
Build type-safe global state in React with Zustand. Supports TypeScript, persist middleware, devtools, slices pattern, and Next.js SSR with hydration handling. Prevents 6 documented errors. Use when setting up React state, migrating from Redux/Context, or troubleshooting hydration errors, TypeScript inference, infinite render loops, or persist race conditions.
90
86%
Does it follow best practices?
Impact
100%
2.32xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms covering both setup and troubleshooting scenarios, explicit 'Use when' guidance, and a clear niche around Zustand state management that distinguishes it from other React or state management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: type-safe global state with Zustand, TypeScript support, persist middleware, devtools, slices pattern, Next.js SSR with hydration handling, and preventing 6 documented errors. Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (build type-safe global state with Zustand, supports TypeScript, persist middleware, devtools, slices pattern, SSR) and 'when' (explicit 'Use when' clause covering setup, migration from Redux/Context, and troubleshooting specific error types). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'React state', 'Zustand', 'Redux', 'Context', 'hydration errors', 'TypeScript inference', 'infinite render loops', 'persist race conditions', 'Next.js SSR'. These are all terms developers would naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Zustand state management in React with clear differentiators like slices pattern, persist middleware, and hydration handling. Unlikely to conflict with generic React skills or other state management library skills due to the explicit Zustand focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable Zustand skill with excellent code examples and good progressive disclosure. Its main weaknesses are moderate verbosity from repeated patterns and explanatory text that Claude doesn't need, plus a lack of explicit sequenced workflows with validation checkpoints for multi-step operations like store setup or migration. The Known Issues section is a strong differentiator, providing real error messages mapped to concrete solutions.
Suggestions
Remove redundant TypeScript store examples—the pattern appears in Quick Start, Core Patterns, and Issue #2. Consolidate to one canonical example and reference it.
Add a sequenced workflow with validation steps for common multi-step tasks (e.g., 'Setting up Zustand in Next.js with persistence': install → create store → add hydration → test SSR → verify devtools).
Trim 'Why It Happens' explanations to single sentences—Claude can infer causation from the error and fix pattern without paragraph-length explanations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~350 lines) with some redundancy—the TypeScript store pattern appears three times (Quick Start, Core Patterns, and Issue #2). The 'Why It Happens' explanations for each issue add context Claude could infer, and some issues like #3 (import error) and #6 (just upgrade) are thin on substance relative to their verbosity. However, most content is code-heavy and actionable rather than purely explanatory. | 2 / 3 |
Actionability | Nearly every pattern and issue includes fully executable, copy-paste-ready TypeScript/TSX code. The code examples are complete with proper imports, type definitions, and realistic usage patterns. The ❌/✅ comparisons make the correct approach immediately clear. | 3 / 3 |
Workflow Clarity | The skill covers individual patterns well but lacks explicit multi-step workflows with validation checkpoints. For example, setting up a new Zustand store in a Next.js project could benefit from a sequenced workflow (install → create store → add hydration handling → verify). The Known Issues section provides good error→fix mappings but not sequenced processes with validation steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections progressing from Quick Start → Core Patterns → Critical Rules → Known Issues → Middleware → Common Patterns → Advanced Topics. The 'Bundled Resources' section provides clear one-level-deep references to templates, guides, and scripts. Navigation is straightforward with descriptive headers. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- jezweb/claude-skills
- Commit
fa91c34
- 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.