CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zustand-store-ts

Create Zustand stores following established patterns with proper TypeScript types and middleware.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/zustand-store-ts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 a well-organized, concise set of Zustand patterns with mostly concrete code, but its quick-start path is broken by the missing assets/template.ts file and its integration workflow lacks any verification step. Fixing the dangling template reference and adding a validation checkpoint would resolve the largest gaps.

Suggestions

Ship the actual assets/template.ts file (or inline the full template in SKILL.md) — the Quick Start's primary step currently points to a nonexistent file.

Replace the placeholder "// state and actions" in the subscribeWithSelector example with a minimal executable state/action pair so the pattern is copy-paste ready.

Add a validation step to Integration Steps, e.g. '4. Run tests: npm test -- src/frontend/src/store' , and delete the vacuous 'When to Use' filler sentence.

DimensionReasoningScore

Conciseness

The body is lean and pattern-focused, with terse code examples like "export const useMyStore = create<MyStore>()(subscribeWithSelector((set, get) => ({...". Minor trimmable padding exists: the description sentence is repeated verbatim after the H1, and the 'When to Use' section is vacuous filler ("This skill is applicable to execute the workflow or actions described in the overview."). Not 5 because those tokens do not earn their place.

4 / 5

Actionability

Concrete code blocks exist (selector, subscription, state/actions interfaces), but the Quick Start's core instruction — "Copy the template from assets/template.ts" — points to a file that does not exist in the bundle, and the middleware example contains only the placeholder comment "// state and actions". This matches 'some concrete guidance but incomplete; missing key details' rather than the minor-gaps level of 4.

3 / 5

Workflow Clarity

Integration Steps list a sequence (create store in src/frontend/src/store/, export from index.ts, add tests) but include no validation checkpoint — e.g. nothing says to run the tests or verify the store compiles. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, where most checkpoints would be present.

3 / 5

Progressive Disclosure

Scored against the actual bundle: no references/, scripts/, or assets/ directories exist, yet the Quick Start directs the reader to assets/template.ts — a broken reference that undermines navigation from the overview. Section structure itself is decent, matching 'some structure but could be better organized; references present but not clearly signaled' rather than 4, since the one reference is missing rather than merely unclear.

3 / 5

Total

13

/

20

Passed

Description

65%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 concise, specific to a named library, and highly distinguishable, but it omits any 'when to use' trigger guidance, which caps its completeness and limits its discoverability. Adding an explicit 'Use when...' clause covering state-management phrasings would address the main gaps.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when creating or refactoring Zustand stores, adding global state to a React/TypeScript app, or when the user mentions Zustand or state management.'

Include the natural synonym 'state management' (and 'React state') so users who don't name Zustand directly can still trigger the skill.

Optionally enumerate a second concrete action (e.g. 'add middleware such as subscribeWithSelector') to lift specificity from one action toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Create Zustand stores" names the domain with one concrete action, and "proper TypeScript types and middleware" are modifiers rather than additional actions — matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. Not 4 because only one verb ('Create') is listed, not several specific actions.

3 / 5

Completeness

The 'what' is clear (create Zustand stores with TS types and middleware), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

"Zustand", "stores", "TypeScript types", and "middleware" are the terms users naturally say when needing this skill, giving good keyword coverage. Not 5 because common phrasings like "state management", "React state", or "global state" are absent.

4 / 5

Distinctiveness Conflict Risk

Zustand is a specific named library, so "Create Zustand stores" occupies a clear niche with distinct triggers and minimal conflict risk with other skills. A user mentioning Zustand unambiguously means this skill.

5 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/zustand-store-ts/SKILL.md

Reviewed

Table of Contents

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.