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.

84

1.10x

Quality

77%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/react-state-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause and specific library names make it highly discoverable. The main weakness is the vague 'Master' verb which doesn't convey concrete actions Claude can perform.

Suggestions

Replace 'Master' with specific actions like 'Configure Redux Toolkit stores, implement Zustand state, set up React Query caching, and migrate between state solutions'

DimensionReasoningScore

Specificity

Names the domain (React state management) and lists specific tools (Redux Toolkit, Zustand, Jotai, React Query), but uses vague verb 'Master' rather than listing concrete actions like 'configure stores', 'implement selectors', or 'set up caching'.

2 / 3

Completeness

Clearly answers both what (state management with specific libraries) and when ('Use when setting up global state, managing server state, or choosing between state management solutions') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say: 'Redux Toolkit', 'Zustand', 'Jotai', 'React Query', 'global state', 'server state', 'state management'. These are terms developers naturally use when seeking help with React state.

3 / 3

Distinctiveness Conflict Risk

Clear niche focused specifically on React state management libraries. The named tools (Redux Toolkit, Zustand, Jotai, React Query) create distinct triggers unlikely to conflict with general React skills or other framework skills.

3 / 3

Total

11

/

12

Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable skill with excellent, production-ready code examples covering multiple state management solutions. However, it's overly long for a SKILL.md file, mixing reference documentation with guidance. The content would benefit from splitting detailed patterns into separate files and adding clearer decision workflows for choosing between solutions.

Suggestions

Move detailed pattern implementations (Redux Toolkit, Zustand slices, Jotai, React Query) to separate files like PATTERNS_REDUX.md, PATTERNS_ZUSTAND.md, etc., keeping only quick-start examples in the main skill

Expand the 'Selection Criteria' section into a proper decision tree or flowchart with specific questions to guide solution choice

Remove the 'Core Concepts' table explaining state categories - Claude already understands these concepts

Add validation steps to the migration guide (e.g., 'Verify by checking Redux DevTools shows the same state shape')

DimensionReasoningScore

Conciseness

The skill is comprehensive but includes some unnecessary explanations like the 'Core Concepts' table explaining what local/global/server state are, which Claude already knows. The 'When to Use This Skill' section is also somewhat redundant given the description.

2 / 3

Actionability

Excellent executable code examples throughout - all TypeScript snippets are complete, copy-paste ready, and demonstrate real-world patterns including store setup, slices, hooks, and mutations with proper typing.

3 / 3

Workflow Clarity

While patterns are well-demonstrated, there's no clear workflow for choosing between solutions or migrating. The 'Selection Criteria' is too brief, and the migration guide lacks validation steps to verify the migration worked correctly.

2 / 3

Progressive Disclosure

The content is a monolithic document with all patterns inline. The external resource links at the end are good, but the 5 detailed patterns (200+ lines of code) could be split into separate files with the main skill providing an overview and navigation.

2 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
freekmurze/dotfiles
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.