zustand

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

Quality

79%

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/SKILL.md

Quality

Content

92%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 a tight, well-structured API reference with executable examples and a complete options table; it is efficient and easy to navigate, with only marginal room to tighten the intro.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of padding or re-explained concepts, with only minor instances (the introductory restatement and the v4 caveat) that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code for both basic and nested-slice cases plus a typed API options table covering defaults and overrides.	5 / 5
Workflow Clarity	A simple single-purpose skill with no destructive or batch operations; the numbered usage sequence (create store, create adapter, use) makes the action unambiguous, qualifying for the simple-skill exception.	5 / 5
Progressive Disclosure	A compact, single-purpose skill with no bundle files, organized into clear sections (Installation, Usage, API) with well-placed content and no nested references.	5 / 5
	Total	19 / 20 Passed

Description

66%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 is clear and specific to a well-scoped niche, cleanly answering both what and when, but it lists a single action and relies on narrow technical keywords rather than broader natural trigger phrases.

Suggestions

Add one or two more concrete capabilities (e.g., wiring a vanilla store, selecting a nested slice) to raise specificity.

Broaden trigger terms with natural phrasings a user might say (e.g., "Zustand store", "json-render state", "state backend") beyond the package name.

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ("Zustand adapter for json-render's StateStore interface") but lists only one action, not the several needed for a higher score.	3 / 5
Completeness	Explicitly states both what ("Zustand adapter for json-render's StateStore interface") and when ("Use when integrating json-render with Zustand"), though the trigger clause covers only one scenario.	4 / 5
Trigger Term Quality	Includes precise but niche technical terms ("json-render", "Zustand", "state management", "@json-render/zustand") while missing common natural-language variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Targets a narrow, well-defined niche (the json-render + Zustand adapter) with distinct triggers and minimal risk of matching the wrong skill.	5 / 5
	Total	15 / 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: 0f6798b

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