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.
39
Quality
11%
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
22%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 title with metadata rather than a functional skill description. It lacks concrete actions, meaningful trigger coverage, and explicit usage guidance. The description would fail to help Claude distinguish this skill from other frontend or state management skills in a large skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Zustand stores with TypeScript types, selectors, and middleware configuration'
Include a 'Use when...' clause with natural trigger terms like 'state management', 'React store', 'global state', 'zustand setup', or 'create store'
Expand trigger terms to include variations users might naturally say: 'zustand', 'state store', 'React state management', 'client state'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Zustand Store Creator') without describing any concrete actions. It doesn't explain what creating a Zustand store involves or what specific capabilities are provided. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' is only implied through the trigger terms. There is no explicit 'Use when...' clause or meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'zustand store creator' as a trigger term (duplicated), which is relevant but narrow. Missing natural variations users might say like 'state management', 'create store', 'zustand setup', or 'React state'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Zustand' provides some specificity to distinguish from generic state management skills, but 'Frontend Development' category is broad and could overlap with other React/state management skills. | 2 / 3 |
Total | 6 / 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 an empty template with no actual content about Zustand stores. It contains only meta-descriptions of what a skill should do without any concrete guidance, code examples, or actionable instructions for creating Zustand stores. The content would be completely unhelpful for Claude attempting to assist with Zustand store creation.
Suggestions
Add executable code examples showing basic Zustand store creation patterns (e.g., `const useStore = create((set) => ({ count: 0, increment: () => set((state) => ({ count: state.count + 1 })) }))`)
Include specific patterns for common use cases: async actions, middleware (persist, devtools), selectors, and TypeScript typing
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual Zustand implementation guidance
Add concrete examples of store structure for different scenarios (auth state, form state, API data caching)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Zustand stores. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or examples for creating Zustand stores. The content describes what the skill does abstractly but provides zero executable guidance on how to actually create a Zustand store. | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The skill claims to provide 'step-by-step guidance' but contains no actual steps for creating a Zustand store. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation. | 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
994edc4
- 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.