zustand

Zustand adapter for json-render's StateStore interface. Use when integrating json-render with Zustand for state management via @json-render/zustand.

Quality

91%

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

Quality

Content

100%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.

This is an exemplary lean skill body: executable end-to-end code for both the basic and nested-slice cases, an unambiguous numbered workflow, and a precise options table with no filler. The only nitpick is that the version requirement ('Requires Zustand v5+') is stated inline rather than in a compatibility section, but it is essential dependency information stated in a single line.

Dimension	Reasoning	Score
Conciseness	Every line is operational — install command, one-line version requirement, executable examples, and a compact options table — with no explanation of concepts Claude already knows and nothing to trim.	5 / 5
Actionability	Fully copy-paste ready: the install command, imports, createStore-to-adapter-to-StateProvider sequence, a nested-slice variant, and typed option defaults with an override example cover the common cases completely.	5 / 5
Workflow Clarity	A simple, single-purpose skill whose create-store → create-adapter → use sequence is unambiguous and explicitly numbered; no destructive or batch operations, so no validation cap applies.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed; the short body is cleanly organized into Installation, Usage (with a nested-slice subsection), and API sections with no inlined content that belongs in separate files.	5 / 5
	Total	20 / 20 Passed

Description

82%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.

A tight, well-scoped description that explicitly states both what the skill does and when to use it, with distinct named-package triggers. Its only weakness is that it names a single capability rather than enumerating the concrete operations the adapter enables.

Dimension	Reasoning	Score
Specificity	Names the domain precisely ('Zustand adapter for json-render's StateStore interface') but describes only one concrete action — wiring a Zustand store as the state backend — rather than the several specific actions of anchor 4.	3 / 5
Completeness	Clearly answers 'what' (adapter for the StateStore interface) and explicitly answers 'when' with a concrete 'Use when integrating json-render with Zustand for state management' trigger clause.	5 / 5
Trigger Term Quality	Includes the natural terms users would say ('Zustand', 'json-render', 'state management', '@json-render/zustand'), but offers no synonyms or variations beyond the proper nouns, falling just short of anchor 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a narrow integration niche named by two specific packages, with trigger phrases that would almost never collide with any other skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/json-render
Path: skills/zustand/SKILL.md
Commit: c2600d7

Reviewed: 1 day 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.