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.

Quality

58%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/react-state-management/SKILL.md

Quality

Content

46%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 skill provides solid, executable code examples across multiple state management libraries, which is its primary strength. However, it suffers from significant verbosity by inlining extensive pattern implementations that should be in referenced files, explains concepts Claude already knows (state categories, basic best practices), and lacks a clear workflow with validation steps for tasks like migration or initial setup.

Suggestions

Move the detailed pattern implementations (Patterns 1-5) into the referenced `resources/implementation-playbook.md` and keep only the Quick Start example and selection criteria in SKILL.md.

Remove the State Categories table and Do's/Don'ts section — these are well-known React concepts that Claude doesn't need explained.

Add a concrete workflow with validation steps for the migration guide (e.g., 1. Identify legacy patterns → 2. Convert one slice → 3. Verify tests pass → 4. Repeat).

Replace the generic Instructions section with specific actionable steps tied to the 'Use this skill when' triggers.

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose at ~300+ lines. It explains state categories (local, global, server, URL, form) that Claude already knows, includes a selection criteria section that's fairly obvious, and provides extensive code examples for five different patterns when a more concise approach would reference a playbook file. The Do's/Don'ts section restates well-known React best practices.	2 / 5
Actionability	The code examples are concrete, executable TypeScript with proper imports and type definitions. The Redux Toolkit, Zustand, Jotai, and React Query patterns are all copy-paste ready. Minor gap: the referenced `resources/implementation-playbook.md` is mentioned but not provided, and some helper functions (fetchUsers, authApi, etc.) are assumed but not defined.	4 / 5
Workflow Clarity	There is no clear multi-step workflow with validation checkpoints. The skill presents patterns as isolated code blocks without a sequenced process for setting up state management, verifying it works, or debugging issues. The 'Instructions' section is generic ('Clarify goals, validate outcomes') rather than providing concrete steps. For a skill covering migration and setup, explicit verification steps would be expected.	3 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` but no bundle files are provided, making this reference unverifiable. The bulk of content (5 full patterns with extensive code) is inlined in the SKILL.md when it clearly should be split into separate files. The patterns section alone is ~200 lines that would be better served by a referenced playbook, with only the Quick Start and selection criteria kept inline.	2 / 5
	Total	11 / 20 Passed

Description

70%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 has a solid 'when' clause and good trigger term coverage through specific library names, making it reasonably effective for skill selection. Its main weakness is the lack of concrete actions — 'Master' is aspirational rather than descriptive of what the skill actually does (e.g., configure stores, create slices, set up queries, migrate between solutions). Adding specific capabilities would significantly improve specificity.

Suggestions

Replace 'Master modern React state management' with concrete actions like 'Configure Redux Toolkit stores, create Zustand stores, set up React Query for data fetching, and implement Jotai atoms'.

Add more natural trigger terms like 'store', 'reducers', 'data fetching', 'caching', or 'atoms' to capture additional user phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain (React state management) and lists specific libraries (Redux Toolkit, Zustand, Jotai, React Query), but the actions are vague — 'master' is not a concrete action. It doesn't describe what the skill actually does (e.g., configure stores, create slices, set up queries).	3 / 5
Completeness	Has both 'what' (React state management with specific libraries) and 'when' ('Use when setting up global state, managing server state, or choosing between state management solutions'). The 'what' could be more concrete about specific actions, but the 'when' clause is explicit and useful.	4 / 5
Trigger Term Quality	Includes strong natural keywords like 'Redux Toolkit', 'Zustand', 'Jotai', 'React Query', 'global state', 'server state', and 'state management'. Missing some variations like 'store', 'reducers', 'atoms', 'caching', or 'data fetching' that users might naturally say.	4 / 5
Distinctiveness Conflict Risk	The specific library names (Redux Toolkit, Zustand, Jotai, React Query) and the focus on state management create a fairly distinct niche. Minor overlap risk with general React skills or individual library-specific skills.	4 / 5
	Total	15 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/react-state-management/SKILL.md
Commit: fbdfd63

Reviewed: 1 day 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.