state-management

Manage client and server state with Zustand stores and React Query patterns.

Quality

66%

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 ./frontend/.claude/skills/state-management/SKILL.md

Quality

Content

81%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 exceptionally concise and well-structured with a genuinely useful decision tree, but its progressive disclosure is undermined by references to bundle files that do not exist, and it offers no executable code examples.

Suggestions

Either create the referenced files (use-zustand-selectors.md, use-zustand-persist.md, use-react-query-for-server.md and the rules/ directory) or remove the dangling references, since pointers to absent files hurt progressive disclosure.

Add a small executable Zustand selector / React Query snippet to the Quick Reference so the core patterns are copy-paste ready rather than only referenced.

If state operations involve mutation/persistence (a near-batch, mutating context), add a brief validation checkpoint (e.g., verify persisted store rehydrates, confirm query invalidation refetches) to lift workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line lead-in, an activation list, a compact Quick Reference table, and a decision tree — with no padding or explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	The decision tree and Quick Reference table give concrete, directly usable routing guidance (which tool for which case, with file references), but there is no executable code/snippet and the Quick Reference points to .md files that do not exist in the bundle, leaving minor gaps.	4 / 5
Workflow Clarity	The decision tree lays out a clear, sequenced routing logic with explicit branches and per-branch annotations (caching/refetching/invalidation, search params, validation), but there are no validation checkpoints or feedback loops, so it stops just short of the top anchor.	4 / 5
Progressive Disclosure	There is clear section structure and one-level-deep references in the Quick Reference table, but the referenced files (use-zustand-selectors.md, use-zustand-persist.md, use-react-query-for-server.md) and the `rules/` directory do not exist in the bundle, so the navigation points to missing material.	3 / 5
	Total	16 / 20 Passed

Description

51%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 moderately specific but lacks an explicit "Use when..." trigger clause and lists only one generic action, capping completeness and specificity. It is reasonably distinctive thanks to named libraries.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers (e.g., global UI state, persisted state, server data fetching/caching, Zustand vs React Query questions).

Replace the single verb "Manage" with several concrete actions (e.g., structure, persist, fetch/cache, invalidate, share cross-component state) to raise specificity.

Include natural user phrasings and synonyms ("global state", "server cache", "client state") alongside the library names to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage client and server state with Zustand stores and React Query patterns" names the domain plus two concrete tools, but lists no discrete actions beyond a single generic verb ("Manage"), so it sits at the 1-2 concrete-actions tier rather than comprehensive coverage.	3 / 5
Completeness	It gives a clear "what" (manage client/server state with Zustand + React Query) but no "Use when..." clause or explicit trigger guidance, so per the rubric a missing explicit-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces the terms users actually say ("client and server state", "Zustand", "React Query") but omits common variations/synonyms like global state, cached server data, or "use state", landing at "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	Naming two specific libraries (Zustand, React Query) carves a fairly distinct niche with only minor overlap against generic React state skills, fitting "mostly distinct; minor overlap risk with closely related skills."	4 / 5
	Total	13 / 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: redpanda-data/console
Path: frontend/.claude/skills/state-management/SKILL.md
Commit: 2deda0a

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.