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.
91
87%
Does it follow best practices?
Impact
95%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche (React useEffect best practices) and provides explicit trigger conditions. The description effectively communicates both the purpose and when to use it, with good coverage of natural developer terminology. Minor improvement could come from listing more specific concrete actions beyond topic areas.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React useEffect) and mentions some actions like 'writing/reviewing useEffect, useState for derived values, data fetching, state synchronization', but doesn't list comprehensive concrete actions - focuses more on topics than specific capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('React useEffect best practices', 'Teaches 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'useEffect', 'useState', 'derived values', 'data fetching', 'state synchronization', 'Effect'. These are terms React developers naturally use when seeking this guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to React useEffect patterns with distinct triggers like 'useEffect', 'useState', 'derived values'. Unlikely to conflict with general React skills or other framework skills due to the specific hook-focused terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured conceptual skill that efficiently teaches when NOT to use useEffect. The quick reference table and decision tree are excellent for rapid decision-making. The main weakness is the lack of concrete code examples showing the correct patterns, which would make the guidance more immediately actionable.
Suggestions
Add 2-3 short executable code snippets showing the 'DO' patterns (e.g., calculating derived state during render, using key prop for reset)
Include a brief before/after code example for the most common anti-pattern (useState + useEffect for derived state)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables and decision trees to convey maximum information with minimal tokens. No unnecessary explanations of React basics Claude already knows. | 3 / 3 |
Actionability | Provides clear conceptual guidance with DON'T/DO patterns and decision tree, but lacks executable code examples. The guidance is specific but not copy-paste ready - no actual React code snippets demonstrating the patterns. | 2 / 3 |
Workflow Clarity | The decision tree provides an excellent clear sequence for determining the right approach. For a conceptual/decision-making skill (not a multi-step process), this is appropriately structured with unambiguous paths. | 3 / 3 |
Progressive Disclosure | Clean overview with well-signaled one-level-deep references to anti-patterns.md and alternatives.md. Content is appropriately split between quick reference and detailed guidance files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- softaworks/agent-toolkit
- Commit
3027f20
- 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.