jotai

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

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.

A model of a small, focused skill: executable examples covering the common cases, a clean API table, and zero padding. Nothing is missing for the adapter's scope.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: no explanation of what Jotai or React are, numbered inline comments instead of prose, and a compact option table. Every section earns its place.	5 / 5
Actionability	Fully executable copy-paste-ready TSX with all imports included, covering both the default case and the shared-Provider case, plus an install command and a complete options table.	5 / 5
Workflow Clarity	Single-purpose skill whose quick-start example lays out an explicit numbered sequence (create atom, create adapter, use it) with no ambiguity; the simple-skill exception applies and no destructive or batch operations require validation checkpoints.	5 / 5
Progressive Disclosure	The skill has no bundle files and needs none — the body is a compact, well-sectioned overview (Installation, Usage, API) with no content that belongs in a separate file and no nested references.	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 concise, well-targeted description with an explicit 'Use when' trigger and concrete package-name keywords. Its only weakness is that it states the adapter's role rather than enumerating the specific capabilities it provides.

Suggestions

Enumerate 1-2 more concrete actions after the role statement, e.g. 'Wires a Jotai atom as the state backend for json-render, sharing state with existing Jotai providers and useAtom() calls.'

Add natural trigger variations such as 'atom', 'state store', or 'Jotai provider' so users phrasing the need differently still match.

Dimension	Reasoning	Score
Specificity	Names the domain precisely ("Jotai adapter for json-render's StateStore interface") but conveys only one implicit action — adapting/wiring state — rather than listing several concrete actions, matching the anchor for domain plus 1-2 actions.	3 / 5
Completeness	Explicitly answers both what ("Jotai adapter for json-render's StateStore interface") and when ("Use when integrating json-render with Jotai for state management via @json-render/jotai") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes the natural terms a user would say ("Jotai", "json-render", "state management", "@json-render/jotai") with good coverage, though common variations like "atom" or "state store" are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche keyed to specific package names (json-render + Jotai); triggers are unambiguous and overlap risk with other skills is minimal.	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/jotai/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.