react-useeffect

React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.

1.02x

Quality

88%

Does it follow best practices?

Impact

95%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is react-useeffect in jarrodwatts/claude-code-config

Quality

Content

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

An efficient, well-organized decision skill that maps situations to concrete React alternatives with no wasted tokens. The main weakness is the two detailed-guidance links point to missing bundle files.

Suggestions

Create the referenced ./anti-patterns.md and ./alternatives.md (or remove the links) so the outbound references actually resolve.

Add one short complete, copy-paste-ready code block contrasting an unnecessary useEffect against the recommended alternative to lift actionability.

Confirm the decision-tree branch for 'Component appeared on screen' maps to a concrete effect example rather than only the category label.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; the one-line intro ("Effects are an escape hatch...") earns its place and every other token drives a decision.	5 / 5
Actionability	Provides concrete actions (useMemo, key prop, useSyncExternalStore, a worked `const fullName = ...` snippet) and a decision tree, but lacks full copy-paste runnable code blocks and defers the deeper examples to bundle files.	4 / 5
Workflow Clarity	The decision tree sequences the reasoning unambiguously (user interaction → event handler; prop change → calculate during render → useMemo; reset → key prop), and as a non-destructive single-purpose decision skill no validation checkpoints are needed.	5 / 5
Progressive Disclosure	Good overview with clearly signaled one-level-deep references (anti-patterns.md, alternatives.md), but those referenced files do not exist, so navigation breaks at the very point it should pay off.	4 / 5
	Total	18 / 20 Passed

Description

87%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 strong description that clearly states both the skill's purpose and its trigger conditions with concrete, natural-sounding keywords. Minor additional synonyms would round out trigger coverage but it already reads as high quality.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "writing/reviewing useEffect", "useState for derived values", "data fetching", "state synchronization" — with minor coverage gaps (no mention of cleanup or lifecycle ordering).	4 / 5
Completeness	Explicitly answers both what ("useEffect best practices... when NOT to use Effect and better alternatives") and when ("Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural terms users say (useEffect, useState, Effect, data fetching, derived values); a few common synonyms such as "React effects" are missing, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (React useEffect guidance) with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	18 / 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
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/react-useeffect/SKILL.md
Commit: cce36d3

Reviewed: about 14 hours 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.