What problem does it solve? Node.js performance issues are hard to diagnose without knowing which profiler answers which question. This Skill guides you to the right built-in Node.js and V8 tool for CPU hotspots, allocation churn, retained memory, GC pressure, and event-loop latency, then shows how to capture and interpret the resulting artifacts correctly. ## Core Features & Use Cases - CPU Profiling: Capture .cpuprofile files with node --cpu-prof or scoped node:inspector sessions, including Deno and Bun variants, and load them in Chrome DevTools. - Memory Analysis: Use node --heap-prof for allocation sampling and v8.writeHeapSnapshot() for retained-heap snapshots, with guidance on sampling intervals and snapshot risks. - GC and Event-Loop Diagnostics: Trace garbage collection with --trace-gc, measure scoped operations with performance.measure(), and quantify event-loop delay with monitorEventLoopDelay(). - Use Case: A Jest test suite feels slow. Run node --cpu-prof ./node_modules/jest/bin/jest.js --runInBand, load the profile in Chrome DevTools, and identify the hot call paths before and after a fix. ## Quick Start Ask the AI to profile your Node.js application's CPU usage with node --cpu-prof and explain the hottest call paths in the generated .cpuprofile.