Lean body with no padding and no explanations of concepts Claude already knows; the only extra note (Zustand v5+ requirement) is a justified constraint, so every token earns its place.

Provides two complete, executable TSX examples and a concrete API options table with types, making the guidance copy-paste ready per the score-3 anchor.

The usage example is explicitly sequenced with numbered steps (// 1, // 2, // 3) and the single-purpose, non-destructive task needs no validation loop; per the simple-skills note this scores 3.

Under 50 lines with no external references needed and no bundle files present; the body is well-organized into Installation, Usage, nested-slice example, and API sections, meeting the score-3 bar for simple skills.

Names the domain and a concrete action ('adapter for json-render's StateStore interface') but does not list multiple specific actions, matching the score-2 anchor rather than the multi-action score-3 example.

Explicitly states both what it does (adapter for the StateStore interface) and when to use it ('Use when integrating json-render with Zustand for state management'), matching the score-3 anchor with an explicit 'Use when' trigger.

Includes relevant natural keywords ('Zustand', 'json-render', 'state management', 'StateStore', '@json-render/zustand') but offers fewer common variations than the score-3 example, which lists multiple phrasings.

A narrow, package-scoped niche (json-render + Zustand integration) with distinct triggers makes conflict with other skills unlikely, matching the score-3 anchor.