zustand-store-ts

Create Zustand stores following established patterns with proper TypeScript types and middleware.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/zustand-store-ts/SKILL.md

Quality

Content

71%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A solid, practical skill that provides clear Zustand store patterns with executable TypeScript examples. Its main weaknesses are the reference to a missing template file (assets/template.ts), the vacuous 'When to Use' section, and the lack of a verification step in the integration workflow. Overall it's well-structured and concise for its scope.

Suggestions

Provide the referenced assets/template.ts file in the bundle, or inline the template content if it's short enough.

Remove or replace the 'When to Use' section with genuinely useful guidance about when Zustand is preferred over other state management approaches in this codebase.

Add a verification step to the Integration Steps, e.g., 'Run tests: npm test -- --testPathPattern=store' to confirm the store works correctly.

Dimension	Reasoning	Score
Conciseness	Generally efficient and assumes Claude's competence with TypeScript and Zustand. The 'When to Use' section at the end is a meaningless tautology that wastes tokens, and the 'Good/Avoid' comments are slightly over-explained but mostly fine.	4 / 5
Actionability	Provides concrete, executable TypeScript code examples for store creation, type separation, selectors, and subscriptions. References a template file (assets/template.ts) with placeholder instructions, but the template itself is not provided in the bundle, creating a minor gap.	4 / 5
Workflow Clarity	The integration steps provide a clear sequence for where to place files. This is a non-destructive, relatively simple skill (creating stores), so the lack of explicit validation/feedback loops is acceptable. However, the steps could mention running tests after creation to verify correctness.	4 / 5
Progressive Disclosure	References assets/template.ts for the template but no bundle files are provided, so we can't verify the reference works. The skill inlines all patterns directly rather than splitting advanced patterns into a separate file, which is borderline acceptable given the content length (~50 lines). The missing bundle file for the referenced template is a notable gap.	3 / 5
	Total	15 / 20 Passed

Description

53%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain (Zustand stores) and mentions TypeScript types and middleware, providing moderate specificity. However, it lacks a 'Use when...' clause, which limits Claude's ability to know when to select this skill. The trigger term coverage is narrow, missing common synonyms and related concepts like 'state management' or 'React state'.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Zustand, state management stores, React global state, or creating typed stores with middleware'.

Expand specific capabilities beyond 'create stores' — mention actions like defining slices, adding persist/devtools middleware, creating selectors, or setting up store hooks.

Include natural synonyms and related terms such as 'state management', 'React state', 'global store', and 'zustand' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Zustand stores) and mentions a couple of concrete aspects (TypeScript types, middleware), but doesn't enumerate specific actions like creating slices, adding persistence, devtools integration, or selectors.	3 / 5
Completeness	Has a clear 'what' (create Zustand stores with TypeScript types and middleware) but completely lacks a 'when' clause or any trigger guidance for when Claude should select this skill.	3 / 5
Trigger Term Quality	Includes 'Zustand stores', 'TypeScript', and 'middleware' which are relevant keywords, but misses natural user phrases like 'state management', 'React state', 'store pattern', 'zustand slice', or 'global state'.	3 / 5
Distinctiveness Conflict Risk	Zustand is a specific library, making this fairly distinct from general state management or other store-related skills. Minor overlap risk with broader React/TypeScript skills, but the Zustand specificity helps.	4 / 5
	Total	13 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/zustand-store-ts/SKILL.md
Commit: 0159794

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.