CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

you-might-not-need-state

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

Quality

77%

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 ./.agents/skills/you-might-not-need-state/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A tight, well-structured instruction skill that encodes genuinely project-specific conventions and gives concrete detection rules with one executable idiom. Its main weaknesses are the total absence of validation after applying fixes and a reference to a rules file that is not present in the bundle.

Suggestions

Add a verification step after fix=true (e.g. run typecheck/tests and confirm no behavior change) so batch edits have a feedback loop.

Inline the essential content of `.claude/rules/sim-hooks.md` (sentinel-on-mount, prev-tracker pattern) into the skill, or move it into a bundle references/ file so the guidance is self-contained.

Add brief before/after code pairs for the highest-frequency patterns (derived state and server-state-in-useState) to make fixes unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and every section earns its place: the Context section encodes project-specific stack ownership ("React Query owns server data, nuqs (URL) owns shareable view-state, Zustand owns global client state") that Claude cannot infer generically, and the seven anti-pattern entries are terse and specific. There is no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Mostly executable guidance: concrete detection rules ("Never `useState` + `useEffect` to sync React Query data"), a copy-paste-ready derive idiom (`items.find(i => i.id === selectedId)`), and specific remediation ("reset with a remount `key`"). Falls short of 5 because fixes for several patterns (derived state, chained Effects) lack before/after examples and there is no instruction to verify fixes (e.g. typecheck/tests).

4 / 5

Workflow Clarity

The three steps (read references, analyze scope, apply or propose fixes) form a clear, unambiguous sequence, but there are no validation checkpoints at all. Since fix defaults to true and the scope can be "whole codebase", batch code edits proceed without any verification step, which caps this dimension at 3.

3 / 5

Progressive Disclosure

At ~30 lines with no bundle files, the body is well-organized into Context, References, Anti-patterns, and Steps, and the three URL references are clearly signaled with their purpose. However, anti-pattern 3 points to `.claude/rules/sim-hooks.md`, which is not part of the skill bundle, making it a dangling reference that a reader cannot resolve from the skill itself.

4 / 5

Total

16

/

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.

A specific, well-scoped description that names concrete actions and the exact React anti-patterns it targets, with strong natural trigger terms like useState and derived state. Its one clear deficiency is the missing 'when to use' clause, which both caps completeness and leaves triggering to inference.

Suggestions

Append an explicit trigger clause, e.g. 'Use when reviewing React code with useState, useSearchParams, or when the user mentions redundant state, derived state, or copying query data into local state.'

Mention 'React' explicitly so the skill surfaces for users who say 'React state' without naming useState.

Add a common variation such as 'redundant state' or 'mirroring props/query data in state' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Analyze and fix unnecessary useState, derived state, and server-state-in-local-state anti-patterns" lists two concrete actions (analyze, fix) plus named pattern categories, matching 'several specific actions; minor gaps in coverage'. Not 5 because coverage is partial (props-mirroring, chained Effects, and object-vs-id patterns are unmentioned) and 'anti-patterns' is a catch-all.

4 / 5

Completeness

The 'what' is clear (analyze and fix these three anti-patterns), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, capping this at 3 per the judging guidelines. Not 4 because 'when' is not merely under-specified — it is entirely absent.

3 / 5

Trigger Term Quality

"useState", "derived state", and "server state" are natural terms a developer would say when needing this skill, matching 'good keyword coverage; a few natural terms missing'. Not 5 because 'React', 'state management', 'redundant state', and common synonyms/extensions are absent; not 3 since the core trigger vocabulary is spot-on.

4 / 5

Distinctiveness Conflict Risk

"unnecessary useState, derived state, and server-state-in-local-state" carves out a clear niche (React local-state anti-patterns) with distinct triggers, and it does not overlap with sibling concerns like URL state (delegated to /you-might-not-need-url-state in the body). Minimal conflict risk with generic code-review skills.

5 / 5

Total

16

/

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.

Validation — 15 / 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

simstudioai/sim

Path

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

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.