做什么
在 JavaScript/Node.js 应用程序中诊断并解析内存泄漏
技能库 智客分类:Agent 工作流 memory-leak-debugging
诊断并解析JavaScript/Node.js应用程序中的内存出漏. 当用户报告内存使用率高,OOM出错,或想与Chrome DevTools MCP内存工具捕获,比较或检查堆积快照时使用.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
在 JavaScript/Node.js 应用程序中诊断并解析内存泄漏
用户报告内存使用率高, OOM 出错, 或想要与 Chrome DevTools MCP 内存工具捕获、比较或检查堆积快照
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Memory Leak Debugging、Prerequisites、Core Principles、Workflows、1. Capturing Snapshots、2. Comparing Snapshots。 其中含规范建议的小节:分步指令。
文件分析:除 SKILL.md 外,正文引用了 references/common-leaks.md,属于带资源的技能包,这些文件按需再读。
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.
Memory Leak DebuggingPrerequisitesCore PrinciplesWorkflows1. Capturing Snapshots2. Comparing Snapshots3. Inspecting Retainers and Dominator Chains4. Advanced Analysis and Categorized Filters
来源分类:skills.sh agent-skill
namememory-leak-debuggingdescriptionreferences/common-leaks.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「memory-leak-debugging」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c481acb4e6a5ec54-%E5%86%85%E5%AD%98%E6%BC%8F%E5%87%BA%E8%B0%83%E8%AF%95.html 请存为 .cursor/skills/memory-leak-debugging/SKILL.md 或 .claude/skills/memory-leak-debugging/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/chromedevtools/chrome-devtools-mcp 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/chromedevtools/chrome-devtools-mcp' --list
npx skills add 'https://github.com/chromedevtools/chrome-devtools-mcp' --skill 'memory-leak-debugging'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
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.
Advanced memory debugging tools (compare_heapsnapshots, get_heapsnapshot_details, 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.
.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.close_heapsnapshot for each loaded snapshot to release memory held by the MCP server.When investigating a frontend web application memory leak, utilize the chrome-devtools-mcp tools to interact with the application and take snapshots.
click, navigate_page, fill, etc. (specifying pageId) to manipulate the page into the desired state.take_heapsnapshot (with pageId) to save .heapsnapshot files to disk at baseline, target (after actions), and final (after reverting actions) states.Once you have generated .heapsnapshot files using take_heapsnapshot, compare them with Chrome DevTools MCP memory tools.
get_heapsnapshot_summary for each snapshot to confirm that the files load and to compare high-level totals.compare_heapsnapshots to compare baseline and target snapshots. Start without classIndex for the summary diff, then request detailed class diffs only for suspicious growth by specifying classIndex.compare_heapsnapshots before drilling into specific node IDs.When a class or object type grows unexpectedly, inspect the retaining chain and dominators with the MCP tools before changing code.
get_heapsnapshot_class_nodes to list instances of the suspicious class.get_heapsnapshot_retainers, get_heapsnapshot_retaining_paths, get_heapsnapshot_dominators, and get_heapsnapshot_edges to understand why representative nodes are still reachable.get_heapsnapshot_object_details with a specific nodeId to retrieve detailed object metadata (size, type, distance, and DOM detachedness).get_heapsnapshot_duplicate_strings when string growth dominates the diff.Use built-in MCP memory tools and filters to pinpoint specific leak categories directly without external tools.
get_heapsnapshot_details or get_heapsnapshot_class_nodes with filterName to target common leak causes:
objectsRetainedByDetachedDomNodes: Identifies detached DOM elements retained in memory.objectsRetainedByEventHandlers: Identifies objects kept alive by unremoved event listeners.objectsRetainedByContexts: Identifies objects trapped in closures or execution contexts.objectsRetainedByConsole: Identifies objects retained by console logging.Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…