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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill zustand-store-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or use cases. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and boilerplate category information add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Zustand stores with TypeScript types, selectors, actions, and middleware configuration'
Include a 'Use when...' clause with natural trigger terms like 'state management', 'React store', 'global state', 'zustand setup', 'create store'
Add context about what problems this solves, e.g., 'Use when building React applications that need lightweight global state management without Redux boilerplate'
| 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 it offers. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('zustand store creator' repeated twice) and overly specific. Missing natural variations users might say like 'state management', 'create store', 'zustand setup', or 'React state'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Zustand' is a specific library which provides some distinctiveness, the lack of detail about what operations it performs could cause confusion with other state management or React-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about Zustand store creation. It contains only generic boilerplate text that could apply to any skill, with no executable code, specific patterns, or actionable guidance for working with Zustand.
Suggestions
Add executable code examples showing how to create a basic Zustand store with TypeScript typing
Include specific patterns for common use cases: async actions, selectors, middleware, persist middleware
Provide a concrete workflow for store creation: define types -> create store -> use in components -> add devtools
Remove all generic boilerplate and replace with Zustand-specific guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Zustand. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance for creating Zustand stores. The content describes what the skill does abstractly rather than providing executable instructions. | 1 / 3 |
Workflow Clarity | No steps, sequences, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, examples, or related documentation. The content is a shallow placeholder with no depth to disclose. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | 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 | 11 / 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.