Download for MacApple silicon, macOS 14+
Skill

ns-memory-spike-analysis

@nodesource Updated 2026-08-28

Diagnoses memory growth, heap spikes, RSS increases, OOMs, and suspected leaks in Node.js apps using supplied heap evidence or N|Solid heap sampling/snapshots. Use when the user reports memory leak, heap growing, high RSS, out-of-memory, heap snapshot/profile analysis, or wants memory root-cause triage.

Install

With your agent

Install OMGSkills skill "nodesource/nsolid-plugin:ns-memory-spike-analysis" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/nodesource/nsolid-plugin /tmp/nsolid-plugin && ln -s /tmp/nsolid-plugin/skills/ns-memory-spike-analysis ~/.claude/skills/ns-memory-spike-analysis

From README

Use Provided Evidence First Parse the prompt for app name, agent ID, asset ID, local heap file path, heap summary, constructor table, retained-size output, or OOM context before calling tools. If the user already provided an asset ID, local file path, or structured heap summary, analyze that evidence first instead of starting with metrics-historic. If the prompt is a telemetry alert for a specific app, use that as the starting signal for live analysis of that same app. If the user explicitly says read-only, offline, or "analyze this file", do not capture a new heap asset unless they later approve it. Find the Bottleneck Only If You Still Need a Target If no agent id is known, call information-dashboard (q: "app= ", start: "5m" when app is known) and preserve the exact app name. Call metrics-historic with field: ["heapUsed", "heapTotal", "rss"], q: "app= " or q: "id= ", and start: "5m". Identify the agent id consistently growing in memory.