What problem does it solve? Slow test suites, plugin-inspector runs, and unexplained memory growth in the OpenClaw codebase waste developer time and obscure real regressions. This Skill replaces guesswork with an evidence-first workflow that baselines wall time, Vitest duration, import cost, CPU, and RSS before and after each fix. ## Core Features & Use Cases - Evidence-Based Benchmarking: Collects wall time, Vitest duration, import breakdowns, max RSS, and CPU metrics using commands like pnpm test:perf:groups and /usr/bin/time -l. - Plugin-Suite Performance Workflow: Maps extension test suites, package-boundary checks, plugin import memory profiles, and Crabbox/Blacksmith Testbox runs for bundled plugin breadth. - Root-Cause Diagnosis: Catalogs common hotspots such as broad SDK barrels, per-test server startup, importActual() mocks, and missing timing fixtures, then fixes causes without losing coverage. - Use Case: A developer notices pnpm test:extensions takes too long. The Skill profiles plugin import memory, identifies a broad plugin-sdk barrel loaded by every plugin-inspector run, moves static metadata into a lightweight artifact, and re-benchmarks to confirm the gain. ## Quick Start Use the openclaw-test-performance skill to benchmark the slowest OpenClaw test files, find the root cause, and report before-and-after wall time and RSS numbers.