state-management
Manage client and server state with Zustand stores and React Query patterns.
51
55%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./frontend/.claude/skills/state-management/SKILL.mdQuality
Discovery
32%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 identifies specific technologies (Zustand, React Query) which helps with targeting, but it lacks concrete actions beyond the vague 'manage state' and completely omits explicit trigger guidance ('Use when...'). It would benefit significantly from listing specific capabilities and adding clear selection criteria.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Zustand stores, React Query setup, global state management, data fetching patterns, or cache invalidation.'
List specific concrete actions like 'Create and configure Zustand stores, set up React Query queries and mutations, handle cache invalidation, implement optimistic updates.'
Include common trigger term variations such as 'TanStack Query', 'global state', 'data fetching', 'caching', 'state management' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (state management) and specific technologies (Zustand, React Query), but 'manage client and server state' is somewhat general and doesn't list concrete actions like 'create stores', 'configure queries', 'handle cache invalidation', etc. | 2 / 3 |
Completeness | Describes what it does (manage state with Zustand and React Query) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good technology-specific keywords ('Zustand', 'React Query', 'stores') that users would naturally mention, but misses common variations like 'state management', 'global state', 'caching', 'data fetching', 'server state', 'TanStack Query'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific libraries (Zustand, React Query) provides some distinctiveness, but 'manage client and server state' could overlap with general React state management skills or other data-fetching pattern skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise decision-making skill that efficiently guides state management choices via a clear decision tree and quick reference table. Its main weakness is the lack of any concrete code examples — all actionable implementation details are deferred to rule files that aren't provided in the bundle. The skill works well as a routing/overview document but would benefit from at least minimal inline code snippets.
Suggestions
Add at least one concrete code example for the most common pattern (e.g., a Zustand store with selector, or a React Query usage) to improve actionability without relying entirely on external files.
Ensure the referenced rule files (use-zustand-selectors.md, use-zustand-persist.md, use-react-query-for-server.md) exist in the bundle, or note their expected paths more precisely to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Zustand or React Query are. The decision tree and quick reference table convey maximum information in minimal tokens. | 3 / 3 |
Actionability | The decision tree provides clear guidance on which tool to use, but there are no concrete code examples, executable snippets, or specific API patterns. All actionable content is deferred to referenced rule files. | 2 / 3 |
Workflow Clarity | The decision tree provides an unambiguous, well-sequenced flow for choosing the right state management approach. For a decision-oriented skill (not a destructive/batch operation), this is clear and complete. | 3 / 3 |
Progressive Disclosure | References to `rules/` directory and specific rule files are present, but no bundle files were provided to verify they exist. The references are one-level deep and clearly signaled, but the lack of actual supporting files and the vague 'See rules/ directory' instruction weakens confidence in navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- redpanda-data/console
- Commit
02210fa
- 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.