CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-leak-audit

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent pattern-catalog skill: six sequenced audit checks with executable BAD/GOOD examples, a quick-reference table, and concrete verification steps including a specific leak-detection command. The only improvements are trimming two rhetorical sentences and optionally moving the detailed per-pattern or chat-specific verification material into a reference file for progressive disclosure.

Suggestions

Trim rhetorical sentences (e.g., "This skill encodes the patterns that prevent and fix leaks" and "A single missed pattern can cause thousands of leaked objects") to push conciseness toward anchor 5.

Consider moving the detailed step-by-step pattern explanations or the chat-specific leak-checker instructions (pnpm run perf:chat-leak details) into a one-level-deep reference file linked from the relevant section, giving the skill a clearer overview-plus-references structure.

Add an explicit error-recovery loop to the Verification section (e.g., "if listener counts still grow, re-run the checklist against the changed code") to make the feedback cycle explicit.

DimensionReasoningScore

Conciseness

The body is lean — tight BAD/GOOD code pairs, repo-specific patterns, and evidence lines rather than concept explanations — but sentences like "This skill encodes the patterns that prevent and fix leaks" and "A single missed pattern can cause thousands of leaked objects" are trimmable rhetoric, matching anchor 4's "minor instances of over-explanation".

4 / 5

Actionability

Every step has copy-paste-ready TypeScript (including a real import path for ensureNoDisposablesAreLeakedInTestSuite), a scenario-to-pattern quick reference table, and a fully specified verification command (pnpm run perf:chat-leak with --messages 20 --verbose and a 2 MB/msg slope threshold) covering the common cases.

5 / 5

Workflow Clarity

"Work through each check in order" establishes an explicit six-step sequence, framed as a checklist, and the Verification section adds explicit validation checkpoints (before/after listener counts, leak-check test suite, heap-growth slope) — matching the anchor-5 combination of checklist plus validation.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and one clearly signaled external reference (the chat-perf skill), but at ~148 lines with no bundle files, organization rests on sections alone; the rubric reserves the sections-only 5 for skills under 50 lines, leaving minor organization gaps at anchor 4.

4 / 5

Total

18

/

20

Passed

Description

91%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 strong description: it states a concrete capability, explicitly lists covered APIs, and provides a clear "Use when" clause with natural trigger terms. The only weaknesses are minor — slightly broad review-oriented triggers and an action list that leans on one verb ("audit") supported by a coverage list.

DimensionReasoningScore

Specificity

"Audit code for memory leaks and disposable issues" plus "Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns" names the domain, a concrete action, and five specific APIs, but lists fewer distinct action verbs than the comprehensive 5-anchor example.

4 / 5

Completeness

Explicitly answers both "what" (audit code for leaks/disposables, covering named patterns) and "when" ("Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user terms ("memory leaks", "leak reports", "event listeners", "DOM handlers", "lifecycle callbacks") plus the exact API names a VS Code developer would say, covering synonyms and variations — comprehensive for this domain.

5 / 5

Distinctiveness Conflict Risk

The leak/disposable niche is clear and mostly distinct, but the trigger "reviewing event listeners, DOM handlers, lifecycle callbacks" is broad enough to occasionally pull in general code-review requests rather than leak-specific ones.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/vscode

Path

.github/skills/memory-leak-audit/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.