Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
Install with Tessl CLI
npx tessl i github:microsoft/agent-skills --skill zustand-storeOverall
score
92%
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 a well-crafted skill description that excels across all dimensions. It provides specific technical capabilities, includes natural trigger terms developers would use, explicitly states both what it does and when to use it, and is highly distinctive due to the Zustand-specific terminology. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create Zustand stores with TypeScript', 'subscribeWithSelector middleware', and 'proper state/action separation'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation') and when ('Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Zustand', 'React state management', 'global stores', 'reactive state patterns'. These cover the primary ways developers would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Zustand' as a specific library name, plus technical specifics like 'subscribeWithSelector middleware'. Unlikely to conflict with generic state management or other React library skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
88%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently teaches Zustand store patterns with executable code and clear organization. The main weakness is the integration workflow lacks explicit validation steps—there's no 'verify your store works' checkpoint or test execution guidance before considering the task complete.
Suggestions
Add a validation step to the Integration Steps section, such as 'Run `npm test src/frontend/src/store/*.test.ts` to verify store behavior' before considering integration complete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanation of what Zustand is or how state management works—assumes Claude's competence. Code examples are minimal but complete. | 3 / 3 |
Actionability | Provides executable TypeScript code for each pattern, a template reference with clear placeholder instructions, and specific file paths for integration. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Integration steps are listed but lack validation checkpoints. No guidance on verifying the store works correctly, running tests, or handling common errors during setup. | 2 / 3 |
Progressive Disclosure | Clean structure with quick start pointing to template file, followed by well-organized sections. References are one level deep and clearly signaled. Appropriate length for inline content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 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 |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.