CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

you-might-not-need-a-callback

Analyze and fix useCallback anti-patterns in your code

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, highly actionable detection guide with concrete anti-patterns, per-pattern fixes, and a correct-use code example that prevents false positives. The main gap is the workflow: fixes are applied by default with no post-fix validation step, which matters when the scope is an entire codebase.

Suggestions

Add a verification step after applying fixes, e.g. "After fixes, run the project's typecheck or tests to confirm behavior is unchanged".

Merge pattern 3 into pattern 1 — both cover handlers passed only to native elements — to remove the redundancy.

Qualify the ".claude/rules/sim-hooks.md" reference so it is only applied when that rules file exists in the target repo.

DimensionReasoningScore

Conciseness

Lean throughout — assumes React competence and explains only the observer rule, which is the crux, not common knowledge. Minor redundancy: pattern 1's "used as a native element handler (`<button onClick={fn}>`)" duplicates pattern 3, and "the reference is unobserved and `useCallback` adds overhead with zero benefit" restates pattern 1's ground.

4 / 5

Actionability

Fully concrete guidance: seven named anti-patterns with inline triggers, a do-not-flag code example for the codebase's ref pattern, and explicit fixes per pattern ("Remove `useCallback`", "Use `useMemo` on the return value instead"). Covers the common cases for an instruction-only skill.

5 / 5

Workflow Clarity

The three-step sequence is clear ("1. Read the reference above / 2. Analyze the specified scope / 3. If fix=true, apply the fixes"), but there is no validation or verification step after applying fixes. With fix defaulting to true and scope reaching "whole codebase", this is batch code modification without a checkpoint, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

A single well-sectioned file with one clearly signaled one-level reference ("Read before analyzing: 1. https://react.dev/reference/react/useCallback"); nothing is inlined that belongs in a separate file. Minor gap: pattern 7 cites ".claude/rules/sim-hooks.md", a project rules file that may not exist in the target repo.

4 / 5

Total

16

/

20

Passed

Description

48%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 names a specific niche and two concrete actions but lacks any explicit "when to use" trigger clause, omits related natural keywords (React, hooks, memoization), and slips into second-person voice ("in your code"). It communicates the what clearly but leaves the when and the trigger surface underspecified.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing React code that uses useCallback, or when the user mentions unnecessary memoization, hook dependency issues, or stale closures."

Include natural synonyms users would say: React, hooks, memoization, React.memo, performance.

Rewrite in third person ("Analyzes and fixes useCallback anti-patterns in React code") to remove the second-person "your code".

DimensionReasoningScore

Specificity

"Analyze and fix useCallback anti-patterns" names the domain and two concrete actions (anchor 3), but "in your code" is second-person voice, which the judging guidelines penalize by reducing the specificity score by 1.

2 / 5

Completeness

The description has a clear "what" ("Analyze and fix useCallback anti-patterns") but no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"useCallback" and "anti-patterns" are natural terms a user would say, but common variations and synonyms (React, hooks, memoization, React.memo, performance) are missing — anchor 3, not the "good keyword coverage" of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"useCallback anti-patterns" is a clear niche with minimal conflict risk, but without elaborated triggers it could overlap with general React performance or refactoring skills — anchor 4, "mostly distinct; minor overlap risk."

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.