you-might-not-need-a-callback

Analyze and fix useCallback anti-patterns in your code

Quality

61%

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-a-callback/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and concise with strong detection criteria and a clear sequence, but it lacks concrete before/after fix examples and a validation checkpoint after applying changes. Both gaps are straightforward to close.

Suggestions

Add before/after code snippets for at least the highest-value fixes (e.g., removing an unobserved useCallback, replacing a returning-new-objects useCallback with useMemo) to make the fix path copy-paste ready.

Insert a validation step in the workflow after applying fixes (e.g., run the test suite or type-check and confirm the component still renders) to add a feedback loop for the batch/destructive fix operation.

Optionally fold the fix remedy for each anti-pattern into a short concrete transformation so detection and remediation stay paired.

Dimension	Reasoning	Score
Conciseness	The body is lean and focused: it states the core rule, lists observers, anti-patterns, and correct patterns without explaining what useCallback or React hooks are. Every section earns its place and it assumes Claude's competence, matching the score-3 anchor.	3 / 3
Actionability	Detection guidance is concrete (seven specific anti-patterns with clear criteria and one executable ref-pattern example), but the fixes are described rather than demonstrated — there are no before/after code transformations, leaving the "fix" path short of copy-paste-ready.	2 / 3
Workflow Clarity	The three-step sequence is clearly listed (read reference, analyze scope, apply or propose fixes), but applying code fixes is a batch/destructive operation with no validation checkpoint (e.g., run tests, verify build), which caps workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	The body is organized into clear sections (References, the rule, anti-patterns, correct patterns, Steps) with a single clearly-signaled one-level-deep URL reference and no nested file chains; navigation is easy and inline content is appropriate for this focused skill.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 specific and names a clear niche, but it answers only the "what" question and omits any explicit "when to use this" trigger guidance. Adding a Use-when clause and more natural trigger keywords would lift all dimensions.

Suggestions

Add an explicit "Use when..." clause naming trigger phrases (e.g., when the user mentions useCallback, React.memo, effect re-running on every render, or hook re-render performance).

Expand concrete actions beyond "Analyze and fix" to include specific outcomes (e.g., detect unnecessary useCallback, remove or refactor to useMemo, fix stale-closure deps).

Include natural keyword variations users would say (React hooks, memoization, re-renders, effect dependency arrays) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Analyze and fix useCallback anti-patterns in your code" names the domain and two actions (analyze, fix), but does not list multiple specific concrete actions like the score-3 example; it is not comprehensive enough to reach 3.	2 / 3
Completeness	It clearly states what the skill does ("Analyze and fix useCallback anti-patterns") but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"useCallback" and "anti-patterns" are natural keywords a React developer would say, but the description misses common variations such as React hooks, memoization, performance, or re-renders, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The "useCallback anti-patterns" niche is fairly specific, but without explicit distinct triggers it could still overlap with general React performance or hooks skills, so it does not meet the clear-distinct-triggers bar for 3.	2 / 3
	Total	8 / 12 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-a-callback/SKILL.md
Commit: 6f514c1

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