you-might-not-need-state

Analyze and fix unnecessary useState, derived state, and server-state-in-local-state anti-patterns

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/you-might-not-need-state/SKILL.md

Quality

Content

80%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 is concise and well-structured with concrete detection guidance, but its workflow applies destructive fixes without a verification checkpoint, capping workflow clarity. Adding a validate-after-fix step would lift the overall score.

Suggestions

Add a verification step after applying fixes, e.g. 'After fixing, run the type checker / test suite and confirm no regressions before reporting done.'

Provide a concrete code transformation pattern for each anti-pattern (before/after) so fixes are copy-paste-ready rather than prose-only.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and well-sectioned, stating crisp rules with one-line rationales and no explanation of basic React concepts Claude already knows.	5 / 5
Actionability	Anti-patterns give concrete detection rules and concrete fixes (e.g. "items.find(i => i.id === selectedId)", "use a key to reset"), but several entries are detection-heavy and fix-light rather than fully copy-paste-ready.	4 / 5
Workflow Clarity	A clear 3-step sequence exists, but since fix=true applies destructive/batch edits with no validation or verification checkpoint, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	An under-50-line single-purpose skill with clean section headers and only one-level-deep external reference URLs; no bundle files are needed, so well-organized sections earn a 5.	5 / 5
	Total	17 / 20 Passed

Description

70%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 specific and distinctive for the React state anti-pattern niche but lacks an explicit "Use when..." trigger clause, which caps its completeness. Strong specificity and distinctiveness; weakest on trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing React components for state misuse, unnecessary useState, or derived/server state copied into local state.'

Include natural synonyms a user might say (e.g. 'React state management', 'state hooks', 'redundant state') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Analyze and fix unnecessary useState, derived state, and server-state-in-local-state anti-patterns" names a concrete domain and several specific actions, but stops short of comprehensive coverage of all state anti-patterns.	4 / 5
Completeness	The "what" is clear but there is no "Use when..." or equivalent trigger clause, so per the missing-trigger guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Concrete technical terms a React developer would say ("useState", "derived state") are present, but common natural synonyms like "React state" or "state management" are missing.	4 / 5
Distinctiveness Conflict Risk	The React-state-specific framing carves a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/you-might-not-need-state/SKILL.md
Commit: 417ae20

Reviewed: 3 days 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.