jotai

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

Quality

87%

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.

The body is an exemplary concise API-reference skill: executable examples, a clear numbered workflow, a typed options table, and tidy sectioning with no bloat. Nothing in the content needs improvement for a skill of this scope.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a single install command, minimal annotated code, and an API table, with no padding or explanations of concepts Claude already knows (atoms, stores, providers).	5 / 5
Actionability	Fully executable, copy-paste-ready code for both the basic and shared-store cases, plus a concrete install command and a complete typed API options table.	5 / 5
Workflow Clarity	The basic usage is a clearly numbered 3-step sequence (create atom, create adapter, use it), and the shared-store variant is a distinct, coherent alternative path; the simple-skill exception applies.	5 / 5
Progressive Disclosure	A short single-purpose skill under 50 lines with no bundle files, organized into well-labeled sections (Installation, Usage, Shared Store, API) — the simple-skill exception for progressive disclosure is satisfied.	5 / 5
	Total	20 / 20 Passed

Description

75%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 well-structured, cleanly answering both what the skill does and when to use it with a distinct, low-conflict niche. The main weakness is trigger-term quality: it relies on technical jargon and a package name rather than the natural phrases a user would say.

Suggestions

Broaden trigger-term coverage with natural-language synonyms a user might say, e.g. 'Jotai state, atom-based state, plugging Jotai into json-render'.

Mention additional concrete capabilities beyond a single 'wire an atom' action (e.g. sharing state with an existing Provider) to lift specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain (adapter) and one concrete action ('Wire a Jotai atom as the state backend'), but coverage is not comprehensive — only a single integration action is described.	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 clause.	5 / 5
Trigger Term Quality	Relevant keywords ('Jotai', 'json-render', 'state management', '@json-render/jotai') are present, but they are all technical/package terms with no natural-language synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	A clearly bounded niche — a Jotai adapter for the specific json-render StateStore interface — with a distinct package name and minimal risk of triggering for unrelated skills.	5 / 5
	Total	16 / 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: 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.