CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

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

The canonical home for this skill is react-state-management in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content delivers highly concrete, executable patterns across the major React state libraries, which is its main strength. Its weaknesses are token inefficiency from inlining ~300 lines of code that belong in reference files, a broken reference pointer, and generic workflow steps lacking validation checkpoints for risky operations like migration.

Suggestions

Move the bulk of the five full pattern implementations into separate reference files (e.g., references/zustand-patterns.md, references/rtk-patterns.md) and keep only a concise Quick Start in SKILL.md, linking out with clearly signaled one-level-deep references.

Fix the broken reference: either create resources/implementation-playbook.md (the path referenced in Instructions) or correct the path to match an existing bundle file.

Replace the generic 'Instructions' boilerplate with a concrete, sequenced workflow that includes validation checkpoints, especially a 'verify the migrated store still dispatches/selects correctly' step in the Legacy Redux to RTK migration section.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but ~430 lines of five complete pattern implementations are inlined where most belong in reference files, and the generic 'Instructions' and 'Do not use this skill when' sections add filler.

3 / 5

Actionability

Concrete, executable TypeScript covers Zustand, RTK, Jotai, and React Query with real patterns like query-key factories and optimistic updates, but undefined referenced types (User, Credentials, UIState) leave minor gaps that prevent fully copy-paste-ready code.

4 / 5

Workflow Clarity

Decision heuristics in 'Selection Criteria' help, but the 'Instructions' steps are generic boilerplate with no real checkpoints, and the risky 'Legacy Redux to RTK' migration has no validation or verification step.

3 / 5

Progressive Disclosure

Section structure exists and one reference is named ('resources/implementation-playbook.md'), but that file does not exist in the bundle, and large pattern blocks that should live in separate reference files are inlined in SKILL.md.

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 concisely states a clear niche with named tools and provides explicit 'Use when' trigger guidance covering the main scenarios. The only weakness is the vague 'Master' framing and a few missing natural trigger variations.

DimensionReasoningScore

Specificity

Lists several concrete actions ('setting up global state, managing server state, choosing between state management solutions') plus four named libraries, but the opening 'Master modern React state management' is a vague framing rather than a concrete action, leaving a minor gap below comprehensive.

4 / 5

Completeness

It explicitly answers both what ('Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query') and when ('Use when setting up global state, managing server state, or choosing between state management solutions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'setting up global state' and 'managing server state' plus library names give good keyword coverage, but common variations like 'optimistic updates' or 'state migration' are missing, falling short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to React state management with specific named libraries and distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.