Name: openclaw-test-heap-leaks
Rating: 64 (1 reviews)
Author: openclaw

Blog Docs Log in Get started

openclaw-test-heap-leaks

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

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/openclaw-test-heap-leaks/SKILL.md

Quality

Content

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

The content is highly actionable with executable commands, a clearly sequenced and verified workflow, and well-organized progressive disclosure via a real bundled script. The main gaps are minor: a missing explicit error-recovery loop in the workflow and some inlined snapshot-usage detail that could live in a reference file.

Suggestions

Add an explicit validate→fix→retry feedback loop in the workflow (e.g., if the re-run does not show reduced RSS, return to Classify and re-inspect retainers) to push workflow_clarity toward 5.

Move the detailed snapshot-comparison flag usage and the runtime-fix harness modes into a short references/ doc, keeping the body as a concise overview that links out, to lift progressive_disclosure.

Tighten a few repetitive phrasings (e.g., repeated full paths to heapsnapshot-delta.mjs) to push conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich with every line carrying actionable domain specifics (config names, script paths, classification heuristics) and assumes Claude's competence without explaining what Vitest or RSS is; it is efficient with only minor phrasing that could be trimmed, landing just below the lean/5 anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (pnpm test:perf:groups with config/output flags, /usr/bin/time -l pnpm test <file> --maxWorkers=1, the snapshot delta invocation with --top/--min-kb/--pid flags), with concrete examples covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence (Reproduce → Collect evidence → Classify → Fix → Verify) with an explicit verification checkpoint (re-run and confirm the max-RSS trend/OOM is reduced); it stops short of 5 because there is no explicit validate→fix→retry error-recovery loop for the batch/grouped operations.	4 / 5
Progressive Disclosure	Well-organized sections and the one bundle file (scripts/heapsnapshot-delta.mjs, a real 556-line script) is referenced repeatedly with clear one-level-deep paths; it sits at 4 rather than 5 because some snapshot-comparison usage detail is inlined in the body rather than moved to a separate reference doc, and no references/ directory is used.	4 / 5
	Total	17 / 20 Passed

Description

70%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 is specific, distinctive, and rich in natural domain trigger terms, but it lacks an explicit "Use when…" clause, which caps its completeness at 3. Adding explicit trigger guidance would raise the overall score meaningfully.

Suggestions

Add an explicit 'Use when …' clause stating the situations that should trigger this skill (e.g., 'Use when investigating pnpm/Vitest test OOMs, rising test RSS, or unexplained heap growth').

Replace or augment the single verb 'Investigate' with distinct concrete actions (e.g., 'Reproduce, collect heap snapshots, classify, and fix OpenClaw pnpm test memory leaks') to push specificity toward 5.

Add a couple of natural synonyms or file extensions users might mention (e.g., '.heapsnapshot', 'worker memory', 'test memory leak') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the specific domain (OpenClaw pnpm test memory) and lists several concrete investigation targets — "memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas" — but uses the single umbrella verb "Investigate" rather than multiple distinct action verbs, so it does not reach the comprehensive multi-action anchor of 5.	4 / 5
Completeness	It has a clear "what" but no explicit "Use when…" clause or equivalent trigger guidance, and per the rubric guidelines a missing explicit trigger clause caps completeness at 3; the "when" is only weakly implied.	3 / 5
Trigger Term Quality	Includes good natural phrases users would say in this niche ("pnpm test memory growth", "Vitest OOMs", "RSS spikes", "heap snapshot deltas") with some variation, though it leans technical and omits common synonyms/extensions, keeping it just below the comprehensive-coverage anchor of 5.	4 / 5
Distinctiveness Conflict Risk	It carves out a clear niche (OpenClaw test heap-leak investigation) with distinct triggers (Vitest OOMs, heap snapshot deltas) and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
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
Commit: ff599bc

Reviewed: 4 days 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.