react-state-management

Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.

1.10x

Quality

72%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/frontend-mobile-development/skills/react-state-management/SKILL.md

The canonical home for this skill is react-state-management in wshobson/agents

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 content provides strong, executable code patterns across the major React state libraries, but as a monolithic 430-line reference it includes generic best-practice padding Claude already knows and does not progressively split detailed material into separate reference files.

Suggestions

Trim the generic Do's/Don'ts list and the Core Concepts table to non-obvious guidance only, removing React fundamentals Claude already knows.

Split the per-library patterns and the legacy-Redux migration guide into separate reference files (e.g. PATTERNS/rtk.md, zustand.md, jotai.md, react-query.md, MIGRATION.md) and keep SKILL.md as a concise overview with one-level-deep links.

Either add a short decision/workflow sequence with a validation checkpoint (e.g. 'select category → implement → verify with React DevTools / type-check'), or reframe the skill explicitly as a reference catalog so workflow clarity expectations align.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code, but the generic Do's/Don'ts ('Colocate state', 'Use selectors', 'Type everything') and parts of the Core Concepts table restate React knowledge Claude already has, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Multiple complete, copy-paste-ready TypeScript blocks (Zustand store, RTK slice, Jotai atoms, React Query optimistic-update hook) cover the common cases, with minor gaps from undefined helper types/functions (User, Credentials, authApi, fetchUsers).	4 / 5
Workflow Clarity	This is a patterns catalog rather than a procedural workflow, so the logical section order (When to Use → Core Concepts → Quick Start → Patterns → Best Practices → Migration) gives a sequence but lacks explicit validation checkpoints or feedback loops.	3 / 5
Progressive Disclosure	It is a single ~430-line file with clear section headers but everything inlined; patterns and the migration guide that could each be separate one-level reference files are not split out, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

87%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 strong: it names concrete tools and actions, explicitly answers both 'what' and 'when' with natural trigger phrases, and carves out a distinct niche. Minor gap is a few missing common synonyms like 'app state' or 'store'.

Dimension	Reasoning	Score
Specificity	Names the domain plus four specific solutions (Redux Toolkit, Zustand, Jotai, React Query) and three concrete actions in the 'Use when' clause ('setting up global state, managing server state, or choosing between state management solutions'), matching the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	Explicitly states both what ('Master modern React state management with...') and when ('Use when setting up global state, managing server state, or choosing between state management solutions') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms a developer would say ('global state', 'server state', 'state management solutions') alongside the library names, giving good keyword coverage, though a few synonyms (e.g. 'app state', 'client state', 'store') are missing.	4 / 5
Distinctiveness Conflict Risk	The React state-management niche with named libraries has distinct triggers and minimal overlap with unrelated skills, fitting the 'clear niche; minimal conflict risk' anchor.	5 / 5
	Total	18 / 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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/frontend-mobile-development/skills/react-state-management/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.