you-might-not-need-a-callback

Analyze and fix useCallback anti-patterns in your code

Quality

64%

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%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 lean, well-structured, and gives a reviewer concrete, specific guidance with a clear code example. Its main weakness is the workflow: applying fixes by default across an arbitrary scope lacks any validation or verification checkpoint.

Suggestions

Add a validation step after applying fixes, e.g. run the test suite or type-check and confirm the app still renders before reporting success.

Require confirmation or a dry-run when scope is large (e.g. 'whole codebase') before mutating many files with fix=true.

Provide at least one full before/after refactor example for a representative anti-pattern (e.g. removing a redundant useCallback) to lift actionability to fully executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude knows React/JSX, with only minor restatement of the core rule, fitting the score-4 anchor of efficient content with light trim potential.	4 / 5
Actionability	A concrete decision rule, seven named anti-patterns with detection criteria, a do-not-flag list, and an executable ref-pattern example give mostly executable guidance, though per-pattern fix refactors are only sketched.	4 / 5
Workflow Clarity	The three-step sequence is coherent, but the skill defaults to fix=true (modifying code, potentially across a whole-codebase scope) with no validation or verification step, so the batch/destructive cap of 3 applies.	3 / 5
Progressive Disclosure	The under-50-line body is cleanly sectioned and self-contained, with a single one-level-deep external reference clearly signaled and no bundle files, satisfying the simple-skill exception for a top score.	5 / 5
	Total	16 / 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 concise and clearly scoped to a distinct niche, but it lacks an explicit "Use when..." trigger clause and broader trigger-term coverage, which limit its completeness and trigger-term scores.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when reviewing React components for unnecessary useCallback usage or callback memoization.'

Broaden trigger terms with synonyms users might say — 'memoization', 'callback', 're-render performance', 'React.memo'.

Optionally mention detection scope (a diff, a file, or the whole codebase) to make the "what" more concrete.

Dimension	Reasoning	Score
Specificity	"Analyze and fix useCallback anti-patterns" names the domain plus two concrete actions (analyze, fix), matching the score-3 anchor of 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The description gives a clear "what" but no explicit "Use when..." trigger clause; per the rubric guideline a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	"useCallback" is the natural term a user would say, but synonyms and variations (memoization, callback, render, performance) are absent, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	"useCallback anti-patterns" is a narrow, specific niche with distinct triggers and minimal overlap risk with other skills.	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-a-callback/SKILL.md
Commit: 417ae20

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.