Agent skill · data analytics · steipete
openclaw-test-performance
Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.
Why this skill is useful
Provides specific benchmarking commands and optimization strategies for OpenClaw that the AI wouldn't reliably generate on its own.
What it needs
Requires pnpm installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Test Performance Use evidence first. The goal is real pnpm test, plugin-suite, and plugin-inspector speed/RSS improvement with coverage intact, not runner tuning by guesswork. Workflow 1. Read the relevant local AGENTS.md files before editing: src/agents/AGENTS.md for agent/import hotspots. src/channels/AGENTS.md and src/plugins/AGENTS.md for plugin/channel laziness. src/gateway/AGENTS.md for server lifecycle tests. test/helpers/AGENTS.md and src/channels/plugins/contracts/test-helpers/AGENTS.md for shared contract helpers. src/infra/outbound/AGENTS.md for outbound/media/action tests. 2. Establish a baseline before changing code: Prefer pnpm test:perf:groups --full-suite --allow-failures --output <file> for full-suite ranking. For bundled plugin breadth, run the smallest relevant pnpm test:extensions:batch <plugin[,plugin...]> or plugin-inspector command before jumping to the full extension sweep. For a scoped hotspot use: /usr/bin/time -l pnpm test <file-or-files> --maxWorkers=1 --reporter=verbose For import-heavy suspicion add: OPENCLAWVITESTIMPORTDURATIONS=1 OPENCLAWVITESTPRINTIMPORTBREAKDOWN=1. 3. Separate wall/runner noise from real file cost: Compare Vitest duration, test body timing, import breakdown, wall time, and max RSS. Re-run single files when grouped/full-suite numbers look stale or noisy. If a full-suite grouped run reports a lane failure but JSON says tests passed, capture that as harness/noise and verify the suspect file directly. 4. Pick the next attack by return and risk: High return: one file/test dominates seconds or RSS and has a clear root. High leverage: one plugin or SDK barrel causes every plugin-inspector or extension-batch run to load broad runtime. Lower risk: static descriptors, target parsing, routing, auth bypass, setup hints, registry fixtures, or test server lifecycle. Higher risk: real memory/runtime behavior, live providers, protocol contracts, or broad production refactors. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-test-performance