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.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

Highly actionable with complete, executable code across all major React state libraries, but the skill is a monolithic 441-line reference that would benefit from splitting patterns into bundle files and replacing generic boilerplate with concrete, checkpointed workflows.

Suggestions

Move the five full pattern code blocks (Redux Toolkit, Zustand slices, Jotai, React Query, combined client/server) into separate reference files under references/ (e.g. REDUX.md, ZUSTAND.md) and keep SKILL.md as a lean overview with one-level-deep links, improving progressive_disclosure and conciseness.

Replace the generic "Instructions" bullets with a concrete selection workflow (assess state category -> choose solution from the Selection Criteria table -> validate via the Best Practices checklist) with explicit validation steps to raise workflow_clarity.

Trim redundant boilerplate such as the "Do not use this skill when" section and inline comments restating obvious behavior to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient actionable code with little concept re-explanation, but at 441 lines it could be tightened and the generic "Instructions" boilerplate ("Clarify goals... Apply relevant best practices... validate outcomes") adds little value, matching the mostly-efficient-but-could-tighten anchor.

2 / 3

Actionability

Provides complete, executable TypeScript for five patterns plus quick start and a before/after migration, all copy-paste ready with real imports and types, matching the fully-executable anchor.

3 / 3

Workflow Clarity

This is a patterns/reference guide rather than a sequenced workflow; the only sequence is the generic Instructions bullets with implicit "validate outcomes" and no concrete validation checkpoints, matching the steps-present-but-checkpoints-missing anchor; not 1 because a sequence does exist.

2 / 3

Progressive Disclosure

Sections are well-organized (Core Concepts, Quick Start, Patterns, Best Practices, Migration, Resources) but everything is inline in SKILL.md with no bundle files, and the five full pattern blocks are content that could be split into separate reference files, matching the some-structure-but-could-better-organize anchor.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong description: specific tools and concrete actions, natural trigger terms, and an explicit Use-when clause in third-person imperative voice. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names concrete actions ("setting up global state, managing server state, or choosing between state management solutions") alongside specific tools (Redux Toolkit, Zustand, Jotai, React Query), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers both what ("Master modern React state management with [tools]") and when ("Use when setting up global state, managing server state, or choosing...") with an explicit Use-when trigger clause.

3 / 3

Trigger Term Quality

Includes natural phrases users would say ("global state", "server state", "Redux Toolkit", "Zustand", "React Query") with good coverage, matching the natural-terms anchor; not above because a few common variations (e.g. "state store", "Redux") are implied rather than listed.

3 / 3

Distinctiveness Conflict Risk

Scoped to React state management with named libraries and specific triggers, giving it a clear niche unlikely to fire for unrelated skills; not a generic overlap risk.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-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.