CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-leaks

Use when reviewing scripts, client components, bundles, or runtime behavior related to Prevent common memory leak patterns. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

70%

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 ./skills/memory-leaks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, well-sectioned rule skill with genuinely actionable check/fix instructions and exemplary progressive disclosure to a real, one-level-deep reference file. Its weaknesses are the opening paragraph restating common knowledge, the absence of any inline code snippet, and no explicit verification loop after fixes are applied.

Suggestions

Trim the two-sentence opening paragraph about what memory leaks are to one sentence of SPA-specific context ("In SPAs where the page is never reloaded, small leaks accumulate per navigation") — Claude already knows what a memory leak is.

Add an explicit validation step after Fix, e.g. "Verify: take a Chrome DevTools heap snapshot before and after the fix and confirm the retained size of the component drops".

Inline one minimal before/after cleanup snippet (removeEventListener in destroy(), or AbortController.abort() on unmount) so the Fix instruction is copy-paste actionable without opening the reference.

DimensionReasoningScore

Conciseness

The body is short (~35 lines) and mostly tight, but the opening paragraph ("Memory leaks cause applications to consume increasing amounts of memory over time, eventually slowing the browser tab or crashing it...") explains a concept Claude already knows, and could be reduced to a single sentence of SPA-specific context. This matches anchor 3 (mostly efficient with some unnecessary explanation) better than anchor 4, since the unnecessary explanation is a full two-sentence passage rather than a minor parenthetical.

3 / 5

Actionability

The Check section enumerates exact patterns to look for ("uncleaned event listeners, retained DOM references after removal, closures holding large objects, and uncleared timers") and the Code Review section names concrete artifacts ("exact imports, event handlers, runtime side effects, or blocking operations"), giving specific executable guidance for an instruction-only skill. It is not anchor 5 because no copy-paste-ready example (e.g. an AbortController or removeEventListener snippet) appears in the body itself — all code is deferred to the reference.

4 / 5

Workflow Clarity

The Check → Fix → Code Review sections imply a rough analyze-then-fix sequence, and verification is mentioned only in passing ("state how the change should be verified in the browser"), but there are no explicit validation checkpoints or feedback loops (e.g. re-check with a DevTools heap snapshot after fixing). This matches anchor 3 (sequence present but checkpoints missing or implicit); it is above anchor 2 because the task modes themselves are clearly and unambiguously defined.

3 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview and the single external reference is clearly signaled, one level deep, and appropriately split: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and references/rule.md exists and does contain the implementation details and code examples promised. This matches anchor 5 (clear overview with well-signaled one-level-deep references, content appropriately split).

5 / 5

Total

15

/

20

Passed

Description

62%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 has an explicit 'Use when' clause and a recognizable niche, but suffers from an obvious template-substitution grammar error ('related to Prevent common memory leak patterns') and thin coverage of the natural trigger phrases users would say when hunting leaks. It functions but reads as machine-assembled and would benefit from a rewrite.

Suggestions

Fix the grammatical break by rewriting the trigger clause, e.g. "Use when reviewing scripts, client components, bundles, or runtime behavior for memory leaks" instead of "related to Prevent common memory leak patterns".

Add natural trigger synonyms users would actually say: event listeners not cleaned up, timers/setInterval, cleanup on component destroy, growing memory usage, page slowdown over time.

Lead with a clear third-person 'what' statement (e.g. "Identifies and fixes common JavaScript memory leak patterns...") before the 'Use when' clause so the capability is stated independently of the trigger.

DimensionReasoningScore

Specificity

The description names the domain ("Prevent common memory leak patterns") and one or two concrete actions ("Inspect both source code and the browser execution path so fixes target the real bottleneck or bug"), but coverage is not comprehensive and the mid-sentence 'related to Prevent common memory leak patterns' break muddles the action statement. It does not reach anchor 4 because it does not list several distinct specific actions, and it is above anchor 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

Both parts are present: an explicit trigger clause ("Use when reviewing scripts, client components, bundles, or runtime behavior related to...") and a 'what' ("Inspect both source code and the browser execution path so fixes target the real bottleneck or bug"). It is not anchor 5 because the 'what' is partially garbled by the ungrammatical 'related to Prevent common memory leak patterns' phrasing, leaving it less clearly and cleanly delineated than the anchor example; it is above anchor 3 because the 'when' is explicit rather than merely implied.

4 / 5

Trigger Term Quality

Relevant keywords are present ("memory leak patterns", "scripts", "client components", "bundles", "runtime behavior", "browser execution path"), but common variations users would actually say — event listeners, timers/setInterval, cleanup, growing memory usage, performance degradation — are missing. It sits between anchor 3 (relevant keywords, missing synonyms) and anchor 4 (good coverage, a few natural terms missing); the gap is more than 'a few' terms, so 3 fits best.

3 / 5

Distinctiveness Conflict Risk

"memory leak patterns" establishes a clear niche with distinct triggers, and the browser/JavaScript framing narrows it further. There is minor overlap risk with closely related skills (general JavaScript code review or performance optimization) because the broad opener 'reviewing scripts... or runtime behavior' could match general review requests, which keeps it below anchor 5.

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/memory-leaks/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.