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

90%

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

Quality

Content

93%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 high-quality, single-purpose audit skill that is token-efficient, fully actionable with executable code, and well-structured with a quick-reference overview and clear verification steps. The only minor gap is the absence of an explicit in-audit fix→retry loop, though the post-fix verification section largely compensates.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it never explains what a memory leak or event listener is, and every section is actionable BAD/GOOD pairs or a reference table that earns its tokens, assuming Claude's competence throughout.	5 / 5
Actionability	Fully executable, copy-paste-ready TypeScript snippets with exact import paths ('../../../../base/test/common/utils.js') and concrete commands ('npm run perf:chat-leak --messages 20 --verbose') covering the common audit cases.	5 / 5
Workflow Clarity	Six audit checks are clearly sequenced ('Work through each check in order') with a dedicated numbered Verification section providing a validation checkpoint; an explicit fix→re-verify feedback loop during the audit steps themselves is only implicit, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Single self-contained file with a built-in overview layer (the Quick Reference table) and clean section headers; the only external pointer ('chat-perf' skill) is one level deep and clearly signaled, with no nested references.	5 / 5
	Total	19 / 20 Passed

Description

87%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, well-targeted description that clearly states the skill's purpose and trigger conditions with concrete, domain-specific terms. Third-person voice is used correctly and there is no vague fluff or over-claiming.

Dimension	Reasoning	Score
Specificity	Names the domain ('Audit code for memory leaks and disposable issues') and enumerates multiple concrete APIs ('addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns'), giving several specific actions with only minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both what ('Audit code for memory leaks and disposable issues') and when ('Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases ('reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports') with good keyword coverage; a few synonyms (e.g. 'resource leak', 'cleanup') are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The VS Code-specific disposal APIs (addDisposableListener, Event.once, MutableDisposable, onWillDispose) carve a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: .github/skills/memory-leak-audit/SKILL.md
Commit: 9bb0f27

Reviewed: about 21 hours 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.