CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-test-heap-leaks

Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.

Quality

79%

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/openclaw-test-heap-leaks/SKILL.md
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 exemplary operational skill: every command is executable, the workflow has explicit validation and adversarial self-checks, and it adds only repo-specific knowledge Claude could not infer. The only weaknesses are a small amount of duplicated command detail and the inlined runtime-fix harness that could live in its own file.

Suggestions

Deduplicate the heapsnapshot-delta.mjs invocation: state the command and flags once (Snapshot Comparison) and reference it from 'Validating runtime fixes' instead of repeating the block.

Consider moving the 'Validating runtime fixes' harness details (modes, snapshot output dir, fixture guidance) into a references/ file, keeping a two-line pointer plus the pnpm leak:embedded-run command in SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what Vitest or heap snapshots are, and every line carries repo-specific evidence (config names, script paths, artifact files). It stops short of anchor 5 because the heapsnapshot-delta invocation is repeated nearly verbatim in both the 'Snapshot Comparison' and 'Validating runtime fixes' sections and could be trimmed.

4 / 5

Actionability

Guidance is fully executable: exact pnpm commands with flags and output paths ('pnpm test:perf:groups --config test/vitest/vitest.unit-fast.config.ts --allow-failures --output ...'), a copy-paste ready /usr/bin/time incantation, and concrete script invocations with useful flags (--top 40, --min-kb 32, --pid 16133). These cover the common cases directly.

5 / 5

Workflow Clarity

The five-step workflow is clearly sequenced (reproduce, collect evidence, classify, fix, verify) with an explicit verification step ('Re-run the same grouped or scoped command and confirm the max-RSS trend or OOM is reduced') and feedback loops — e.g., the closure-inline and synthetic-leak harness modes that validate the detector before trusting a PASS. Ambiguity handling ('stop short of a confident label and inspect retainers') adds an error-recovery path.

5 / 5

Progressive Disclosure

The bundle's one script (scripts/heapsnapshot-delta.mjs) is well-signaled with usage shown inline, and the body is organized into clear sections (Workflow, Heuristics, Snapshot Comparison, runtime-fix harness, Output Expectations). It does not reach anchor 5 because the ~30-line 'Validating runtime fixes' harness section is a semi-separate concern inlined in SKILL.md, and the pointer to the sibling skill '../openclaw-test-performance/SKILL.md' is a cross-skill reference rather than a bundled one-level-deep reference.

4 / 5

Total

18

/

20

Passed

Description

61%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 tight, domain-specific description with concrete trigger terms but limited action coverage and no explicit 'when to use' guidance. Adding a 'Use when...' clause and one or two more action verbs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when Vitest workers OOM, max RSS trends upward across shards, or heap snapshots show retention growth.'

Expand beyond the single verb 'Investigate' to name the key actions the skill performs, such as comparing heap snapshots per PID and classifying growth as worker-lifetime retention vs. real leaks.

Include common user synonyms like 'memory leak' and 'out of memory' alongside 'OOMs' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and concrete artifacts ('Vitest OOMs, RSS spikes, and heap snapshot deltas') but relies on a single action verb ('Investigate'), offering only 1-2 concrete actions rather than a comprehensive list of capabilities. It does not reach anchor 4, which expects several specific actions listed.

3 / 5

Completeness

The 'what' is clear (investigate test memory growth, OOMs, RSS spikes, snapshot deltas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Phrases like 'pnpm test memory growth', 'Vitest OOMs', 'RSS spikes', and 'heap snapshot deltas' are natural terms a user would say when hitting this problem. It falls short of anchor 5 because common synonyms such as 'memory leak' or 'out of memory' are absent.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to 'OpenClaw pnpm test' heap/memory diagnostics, giving it a clear niche with minimal conflict risk. Anchor 5 is not reached because it could mildly overlap with a sibling test-performance or profiling skill.

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

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/openclaw

Path

.agents/skills/openclaw-test-heap-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.