CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

you-might-not-need-a-memo

Analyze and fix useMemo/React.memo anti-patterns in your code

Quality

72%

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

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.

A tight, well-structured instruction-only skill whose anti-pattern catalog is genuinely actionable and whose size and organization are exemplary. Its main weakness is the absence of any validation step before or after applying fixes across potentially large scopes, which the rubric caps at workflow clarity 3.

Suggestions

Add a verification step after applying fixes, e.g. "4. Run the project's tests/linter (or typecheck) on the changed files; if anything breaks, revert the fix and propose it instead" — this both uncaps workflow clarity and guards batch edits.

Include a short before/after code pair for one or two patterns (e.g. state moved down into a child) to make the fixes copy-paste concrete rather than descriptive.

State how to resolve each scope value into a concrete file set (e.g. which git command produces "diff to staging"), since step 2 currently leaves the mechanics implicit.

DimensionReasoningScore

Conciseness

The body is lean: each anti-pattern is a compact detection rule plus fix, and the do-not-flag exception is one line, matching anchor 4's "efficient; minor instances of over-explanation". Minor trimmable spots exist, e.g. "Children passed as props don't re-render when the parent's state changes" and "React.memo's shallow comparison always fails" restate React behavior Claude already knows. Not 5 because of those few redundant explanation fragments; not 3 because there is no padded or unnecessary section.

4 / 5

Actionability

Each of the seven anti-patterns pairs a concrete detection criterion with a specific fix ("move that state into a smaller child component", "Fix the deps or remove the memo"), and scope examples ("diff to staging", "PR #123") make the argument handling concrete — anchor 4. Not 5 because there are no before/after code examples and no commands for resolving a scope; not 3 because the guidance is specific and executable as written, not pseudocode.

4 / 5

Workflow Clarity

The three steps are clearly sequenced (read reference → analyze scope → apply or propose fixes), but with fix=true defaulting on and scope able to be "whole codebase", edits are applied across many files with no validation or verification step (no test/build/linter check), which the rubric caps at anchor 3. Not 4 because the missing checkpoint is material for a batch-edit workflow, not a minor gap; not 2 because the sequence itself is complete and unambiguous.

3 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (References, Anti-patterns to detect, Patterns that ARE correct, Steps) and a single clearly-signaled one-level-deep reference ("Read before analyzing" → the overreacted.io article), and the two core techniques are also summarized inline. Per the rubric's simple-skill guideline this matches anchor 5; there are no bundle files to mis-navigate and no inlined content that belongs elsewhere.

5 / 5

Total

16

/

20

Passed

Description

60%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 concise, distinctive description with strong natural trigger terms, but it omits any explicit "when to use" guidance and uses second-person voice ("in your code"), which costs it specificity under the rubric. Adding a trigger clause and third-person phrasing would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions useMemo, React.memo, memoization, or unnecessary re-renders" — the missing 'when' currently caps completeness at 3.

Rewrite in third person to remove the second-person "in your code" (e.g. "...anti-patterns in React code"), which the rubric penalizes by one specificity point.

Include synonyms like "memoization", "re-render", and "performance" to broaden natural keyword coverage from good to comprehensive.

DimensionReasoningScore

Specificity

The description names the domain ("useMemo/React.memo anti-patterns") with two concrete actions ("Analyze and fix"), which matches anchor 3; however, the rubric mandates a 1-point reduction for second-person voice, and "in your code" addresses the user directly, dropping it to anchor 2. Not anchor 1 because the domain and actions are still concrete, not generic.

2 / 5

Completeness

The "what" is clear ("Analyze and fix useMemo/React.memo anti-patterns"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at anchor 3. Not 4 because the "when" is entirely missing rather than just imprecise.

3 / 5

Trigger Term Quality

"useMemo/React.memo" and "anti-patterns" are exactly the terms a user would naturally say when needing this skill, matching anchor 4's good coverage. Not 5 because common variations like "memoization", "re-render", or "performance" are absent; not 3 because the exact API names are stronger triggers than anchor 3's single generic keyword.

4 / 5

Distinctiveness Conflict Risk

"useMemo/React.memo anti-patterns" carves out a clear niche with distinct triggers and minimal overlap with any plausible sibling skill, matching anchor 5. It is clearly more specific than anchor 4's "minor overlap risk with closely related skills".

5 / 5

Total

14

/

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-memo/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.