CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean skill body built on executable BAD/GOOD code pairs, an ordered audit checklist with explicit test-validation, and a verification checklist with concrete thresholds. It assumes Claude's competence and stays highly actionable throughout.

DimensionReasoningScore

Conciseness

Lean BAD/GOOD code pairs with terse rules and no explanation of basic concepts Claude already knows; the 'Validated by' lines and Quick Reference table are scannable aids, not padding. Not 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides executable TypeScript with exact import paths and concrete commands such as 'npm run perf:chat-leak --messages 20 --verbose', copy-paste ready. Not 2 because the examples are complete and executable, not pseudocode.

3 / 3

Workflow Clarity

Sequences an ordered 6-step audit checklist with a dedicated test-validation step and a Verification section containing explicit thresholds (slope > 2 MB/msg). Not 2 because validation checkpoints are explicit, not missing or implicit.

3 / 3

Progressive Disclosure

A self-contained pattern catalog with well-organized sections (When to Use, Audit Checklist, Quick Reference, Verification) and a single clearly-signaled cross-skill pointer (chat-perf); no bundle files exist, so well-organized sections suffice. Not 2 because structure and navigation are clear rather than disorganized.

3 / 3

Total

12

/

12

Passed

Description

100%

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, third-person description that states a concrete capability, lists specific covered APIs, and provides an explicit 'Use when' trigger clause covering several natural phrasings. It is concise and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

States the concrete action 'Audit code for memory leaks and disposable issues' and enumerates specific APIs (addDisposableListener, Event.once, MutableDisposable, DisposableStore, onWillDispose), matching the 'lists multiple specific concrete actions' anchor. Not 2 because it names exact APIs rather than just a domain.

3 / 3

Completeness

Explicitly answers what ('Audit code for memory leaks and disposable issues') and when ('Use when reviewing event listeners... or fixing leak reports') with an explicit 'Use when' clause. Not 2 because the trigger guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

Includes natural developer phrases a user would actually say — 'reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports' — giving good coverage. Not 2 because multiple common variations are present rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow VS Code disposable/leak niche with highly specific API names, making it unlikely to fire for unrelated skills. Not 2 because the niche and triggers are clearly distinct, not broadly overlapping.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.