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.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill zustand-state-managementOverall
score
90%
Does it follow best practices?
Validation for skill structure
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, uses natural developer terminology as trigger terms, explicitly states both what it does and when to use it, and carves out a clear niche around Zustand specifically. The mention of '6 documented errors' and specific error types like 'hydration errors' and 'persist race conditions' makes it highly actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: 'Build type-safe global state', 'Supports TypeScript, persist middleware, devtools, slices pattern, and Next.js SSR with hydration handling', and 'Prevents 6 documented errors'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (build type-safe global state with Zustand, supports various features) AND when with explicit 'Use when...' clause covering setup scenarios, migration paths, and specific troubleshooting triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'React', 'Zustand', 'TypeScript', 'Redux', 'Context', 'hydration errors', 'infinite render loops', 'persist race conditions', 'Next.js SSR'. These match how developers naturally describe their problems. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Zustand (not generic state management), mentions specific error types and patterns unique to this library. Unlikely to conflict with general React or Redux skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-organized skill with excellent actionability - every pattern includes executable code. The structure follows good progressive disclosure with clear navigation. The main weakness is verbosity in the 'Known Issues' section where 'Why It Happens' explanations could be trimmed since Claude can infer causation from the error and prevention code.
Suggestions
Trim or remove 'Why It Happens' explanations in the Known Issues section - the error message and prevention code are sufficient for Claude to understand the issue
Condense the issue descriptions by removing phrases like 'This skill prevents 6 documented issues' and verbose source citations - a simple link suffices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient with good code examples, but includes some unnecessary explanations (e.g., explaining what persist middleware does, verbose issue descriptions). The 'Why It Happens' sections add bulk that Claude could infer. | 2 / 3 |
Actionability | Excellent executable code throughout - all examples are copy-paste ready TypeScript/JavaScript with proper imports. The prevention patterns for each issue are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequences for complex patterns like slices and middleware composition. The hydration pattern includes explicit validation (check hasHydrated before rendering). The Critical Rules section provides clear do/don't guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with Quick Start → Core Patterns → Critical Rules → Known Issues → Advanced Topics progression. References bundled templates and separate markdown files for detailed topics without nesting. Easy navigation with clear section headers. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.