you-might-not-need-an-effect

Analyze and fix useEffect anti-patterns in your code

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/you-might-not-need-an-effect/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, well-structured, and gives actionable guidance, but the fix-applying workflow lacks validation/verification checkpoints despite mutating code. Adding a verify step before and after applying fixes would raise workflow clarity.

Suggestions

Add an explicit validation/verification checkpoint (e.g., run the test suite or type-check after applying fixes, and re-analyze to confirm the anti-pattern is gone).

Provide a concrete detection recipe for finding useEffect anti-patterns in the scope (e.g., a grep pattern or lint command) rather than delegating fully to manual analysis.

Insert a review/dry-run gate before applying fixes even when fix=true, so changes are confirmed before mutation.

Dimension	Reasoning	Score
Conciseness	The body is lean and prescriptive with no padding or explanation of React/useEffect basics; every token earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Provides concrete arguments, a specific external reference URL, and a concrete fix=true/false conditional, plus specific actionable guidance in the Query-backed forms section; it stops short of fully executable code, leaving minor gaps.	4 / 5
Workflow Clarity	The three-step sequence is clear, but the skill applies code changes (a destructive/batch operation) with no validation or verification checkpoint, which per the guidelines caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external bundle references and a clear section header; per the simple-skills note this well-organized content merits a 5.	5 / 5
	Total	17 / 20 Passed

Description

57%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 domain-specific and clearly distinguishable but omits any explicit 'when to use' trigger guidance and lists only two actions. Adding a 'Use when...' clause and naming common anti-patterns would raise completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when reviewing React components for unnecessary or misused useEffect hooks').

Name the concrete anti-pattern categories covered (e.g., 'syncing state, deriving values, fetching without cleanup') to broaden specificity and trigger-term coverage.

Include natural synonyms a user might say ('react effect', 'useEffect dependencies', 'useEffect cleanup') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain ('useEffect anti-patterns') and two concrete actions ('Analyze and fix'), matching the 1-2 concrete actions anchor; it does not enumerate the anti-pattern categories, so it is not a 4.	3 / 5
Completeness	It has a clear 'what' but no 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords ('useEffect', 'anti-patterns') but lacks common natural synonyms users say ('react hook', 'useEffect cleanup', 'dependencies'), so it sits at the 'some relevant keywords' anchor rather than a 4.	3 / 5
Distinctiveness Conflict Risk	'useEffect anti-patterns' is a clear niche with distinct triggers and minimal overlap with other skills, matching the clear-niche anchor.	5 / 5
	Total	14 / 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: 7945b29

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.