memory-leak-debugging
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.
Install
With your agent
Install OMGSkills skill "chromedevtools/chrome-devtools-mcp:memory-leak-debugging" 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/ChromeDevTools/chrome-devtools-mcp /tmp/chrome-devtools-mcp && ln -s /tmp/chrome-devtools-mcp/skills/memory-leak-debugging ~/.claude/skills/memory-leak-debuggingFrom README
Memory Leak Debugging This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools. Prerequisites Advanced memory debugging tools (compareheapsnapshots, getheapsnapshotdetails, etc.) are only available when the server is started with the --memoryDebugging flag. First check if these tools are available; if not, try to read the MCP configuration file to check if --memoryDebugging is enabled. Core Principles Prefer MCP memory tools: Do NOT attempt to read raw .heapsnapshot files directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots. Isolate the Leak: Determine if the leak is in the browser (client-side) or Node.js (server-side).
More from this repo
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines.
chrome-devtools-cli
Used to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via...