you-might-not-need-an-effect

Analyze and fix useEffect anti-patterns in your code

Quality

57%

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-an-effect/SKILL.md

Quality

Content

61%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 body is admirably concise and well-structured for a simple skill, but it relies on an external URL for its actual substance and provides no concrete anti-pattern examples or validation step before applying fixes.

Suggestions

Inline 2-3 concrete anti-pattern-to-fix examples (e.g. deriving state vs. syncing state to props, removing unnecessary effects) so the skill is actionable without round-tripping to the URL.

Add a validation checkpoint after applying fixes (run tests / typecheck / confirm no behavior change) before declaring done.

For fix=false, specify the output format for proposed changes so the proposal is concrete rather than abstract.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every line (Arguments, $ARGUMENTS, the three steps) earns its place.	5 / 5
Actionability	Substantive guidance is delegated to an external URL and the instruction "apply the fixes" is abstract with no concrete code, patterns, or examples, fitting the minimal-concrete-guidance anchor.	2 / 5
Workflow Clarity	A clear three-step sequence exists, but applying fixes across a scope is a batch modification with no validation/verification checkpoint, so per the guidelines workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	This simple under-50-line skill is well organized into Arguments and Steps with a single well-signaled external reference and no nesting; it is not 5 because the core substance lives off-page rather than in well-split local material.	4 / 5
	Total	14 / 20 Passed

Description

53%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 concise and names a clear, distinctive niche with two concrete actions, but it omits any explicit trigger guidance, which caps completeness and leaves trigger-term coverage incomplete.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when reviewing React hooks, useEffect, dependency arrays, or effect cleanup."

Broaden trigger terms to include synonyms users actually say (hooks, effects, dependency array, cleanup, stale closure).

Optionally name 1-2 more concrete actions (e.g. "convert effects to events, remove redundant effects") to lift specificity.

Dimension	Reasoning	Score
Specificity	"Analyze and fix useEffect anti-patterns" names the domain plus two concrete actions, matching the 1-2 action anchor; it is not 4 because it lacks several specific actions or comprehensive coverage.	3 / 5
Completeness	It clearly states what the skill does but has no "Use when..." trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"useEffect anti-patterns" is a natural term developers use, but common synonyms (hooks, effects, dependency array, cleanup) are absent, so it falls at the some-keywords-but-incomplete anchor.	3 / 5
Distinctiveness Conflict Risk	The useEffect-anti-pattern niche is clearly distinct with low conflict risk; "in your code" is slightly generic, keeping it just below the 5 anchor.	4 / 5
	Total	13 / 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-an-effect/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.