zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
35
3%
Does it follow best practices?
Impact
91%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/zustand-store-creator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that repeats the skill name without providing any meaningful information about capabilities, actions, or usage triggers. It lacks concrete actions (e.g., creating stores, defining state slices, configuring middleware), natural trigger terms users would use, and explicit 'Use when...' guidance. The only redeeming quality is that 'Zustand' is a specific enough technology name to provide minimal distinctiveness.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates Zustand stores with typed state, actions, selectors, and middleware configuration for React applications.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about zustand, React state management, creating a store, global state, state slices, or zustand middleware.'
Remove the duplicate trigger term and expand with variations users would naturally say, such as 'zustand', 'state store', 'React global state', 'zustand setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Zustand Store Creator' but does not describe any concrete actions like creating stores, defining slices, setting up middleware, or managing state. It only repeats the skill name without explaining what it actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'zustand store creator' repeated twice. Missing natural variations users would say like 'zustand', 'state management', 'create store', 'React state', 'zustand slice', or 'global state'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Zustand' is fairly specific to a particular state management library, which provides some distinctiveness. However, the vague 'Frontend Development' category and lack of concrete actions could cause overlap with other state management or React-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 placeholder with no substantive content. It contains only meta-descriptions of what the skill would do without any actual instructions, code examples, or concrete guidance for creating Zustand stores. It fails on every dimension because it provides zero actionable information.
Suggestions
Add concrete, executable code examples showing how to create a Zustand store (e.g., basic store, store with slices, store with middleware like immer or devtools).
Include a clear workflow for store creation: define types → create store → add selectors → integrate with components, with specific code for each step.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content about Zustand patterns, best practices, and common pitfalls.
Add references to advanced topics in separate files if needed (e.g., MIDDLEWARE.md for persist/devtools, PATTERNS.md for slice pattern and computed values).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Zustand stores. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no API patterns, no store creation templates, no executable commands. The skill describes rather than instructs, offering nothing Claude could act on. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. | 1 / 3 |
Total | 4 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.