Name: zustand-store-ts
Rating: 56.00000000000001 (1 reviews)
Author: administrakt0r

Blog Docs Log inGet started

zustand-store-ts

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

Quality

64%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zustand-store-ts/SKILL.md

The canonical home for this skill is zustand-store-ts in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

71%Weight 40%Scale 1-5

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

The content is well-structured, concise, and provides solid executable Zustand patterns with a clear integration workflow. Its main weakness is progressive disclosure: the Quick Start depends on an assets/template.ts file that is not bundled, breaking the primary getting-started path.

Suggestions

Either bundle the referenced assets/template.ts so the Quick Start works as written, or inline the template directly in SKILL.md and drop the file reference.

Replace the generic 'When to Use' sentence with concrete trigger conditions for when to reach for this skill.

Make the subscribe example self-contained by defining selectedId in the shown state interface or annotating it as illustrative.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly executable code with little explanatory prose, but it restates the description under the title and includes a vapid "When to Use" filler sentence, fitting the efficient-with-minor-trimmable-instances anchor.	4 / 5
Actionability	Concrete TypeScript examples (subscribeWithSelector, state/action interfaces, selectors, subscribe) and explicit integration paths are mostly executable, but the Quick Start relies on a missing assets/template.ts and the subscribe example references an undefined selectedId, leaving minor gaps.	4 / 5
Workflow Clarity	The Integration Steps give a clear 3-step sequence (create, export, add tests) where the final test step acts as a validation checkpoint; the operation is not destructive so no cap applies, and only minor validation detail is missing.	4 / 5
Progressive Disclosure	Sections are well-organized with no nested references, but the primary Quick Start instruction points to assets/template.ts which does not exist (no bundle files are present), so a clearly signaled reference is broken — the structure is good but a key external pointer is nonfunctional.	3 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%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 clearly identifies its niche (Zustand store creation) but is thin on trigger coverage and omits any explicit "when to use" guidance, leaving it at a middling completeness level. It is distinct and reasonably specific but would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when…' clause naming natural triggers, e.g. 'Use when creating or modifying Zustand stores, adding state management to a React app, or wiring up middleware.'

Expand specificity beyond a single action by listing concrete tasks like 'define typed state/action interfaces, apply middleware, and set up selectors.'

Add common synonyms users say, such as 'state management' and 'React store', to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Create Zustand stores following established patterns with proper TypeScript types and middleware" names the domain plus one concrete action (create stores) with qualifiers (types, middleware), but lists no additional distinct actions, matching the anchor that names the domain with 1-2 concrete actions yet is not comprehensive.	3 / 5
Completeness	The "what" is clear (create typed Zustand stores with middleware) but there is no "Use when…" trigger clause, so per the judging guideline completeness is capped at 3 — a clear what with the when missing.	3 / 5
Trigger Term Quality	"Zustand stores" is a natural term a user would say, but coverage stops there — common synonyms like "state management" or variations are absent, fitting the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Zustand is a specific, named library with a clear niche (store creation with TS types and middleware), giving distinct triggers and minimal overlap with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zustand-store-ts/SKILL.md
Commit: 57c135b

Reviewed: 7 days 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.