[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DRQNH1M2CX03FS815EN9T":3,"skill-same:01M73DRQNH1M2CX03FS815EN9T":47},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M73DRQNH1M2CX03FS815EN9T","memory-leak-detection",null,"Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fmemory-leak-detection\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: memory-leak-detection\ndescription: Node.js memory leak detection and heap profiling. node-memwatch heap diffing, V8 heap snapshots, GC event monitoring, heap growth trending, and leak remediation patterns. Sources: lloyd\u002Fnode-memwatch, Node.js v8 module.\norigin: yana-ai — synthesized from lloyd\u002Fnode-memwatch (BSD-2-Clause), Node.js v8 heap docs\nlicense: Apache-2.0\nversion: 1.0.0\ncompatibility: yana-ai >= 1.3.48\n---\n\n# \u002Fmemory-leak-detection\n\n## When to Use\n\n- Long-running agent sessions accumulating heap without releasing\n- Debugging why sandbox process is OOM-killed after hours of operation\n- Validating that event listeners and streams are properly cleaned up\n- Heap diffing to identify which objects grow between requests\n\n## Do NOT use for\n\n- One-shot scripts (leak only matters for long-running processes)\n- Production traffic interception (heap snapshots block the event loop)\n\n---\n\n## Heap leak detector (memwatch-next)\n\n```javascript\nimport memwatch from 'memwatch-next'\n\n\u002F\u002F 'leak' fires when heap grows 5 consecutive GC cycles\nmemwatch.on('leak', (info) => {\n  console.error('[memwatch] LEAK DETECTED', JSON.stringify(info))\n  \u002F\u002F info: { start, end, growth, reason }\n  \u002F\u002F growth is bytes added since last GC\n})\n\n\u002F\u002F GC stats after every garbage collection\nmemwatch.on('stats', (stats) => {\n  if (stats.current_base > 200 * 1024 * 1024) {  \u002F\u002F 200MB threshold\n    console.warn('[memwatch] heap baseline high:', Math.round(stats.current_base \u002F 1024**2), 'MB')\n  }\n})\n```\n\n---\n\n## Heap diff to find leaked objects\n\n```javascript\nimport memwatch from 'memwatch-next'\n\n\u002F\u002F Perform an action twice, diff heap to see what objects grew\nconst hd = new memwatch.HeapDiff()\n\n\u002F\u002F ... run the suspected leaky operation ...\nawait runAgentSession()\n\nconst diff = hd.end()\nconst growing = diff.change.details\n  .filter(d => d.size_bytes > 0)\n  .sort((a, b) => b.size_bytes - a.size_bytes)\n  .slice(0, 10)\n\nconsole.table(growing.map(d => ({\n  what:   d.what,\n  added:  d['+'],\n  freed:  d['-'],\n  deltaBytes: d.size_bytes,\n})))\n```\n\n---\n\n## V8 heap snapshot (built-in, no dependency)\n\n```javascript\nimport v8 from 'v8'\nimport { writeFileSync } from 'fs'\n\n\u002F\u002F Take a heap snapshot — blocks event loop, do offline\u002Fon-demand only\nfunction takeHeapSnapshot(path = `\u002Ftmp\u002Fheap-${Date.now()}.heapsnapshot`): string {\n  const snapshot = v8.writeHeapSnapshot(path)\n  console.log(`[heap] snapshot written: ${snapshot}`)\n  return snapshot\n  \u002F\u002F Open in Chrome DevTools → Memory tab → Load snapshot\n}\n```\n\n---\n\n## Simple heap trending (no library)\n\n```javascript\nconst heapSamples: number[] = []\n\nfunction sampleHeap(): void {\n  const used = process.memoryUsage().heapUsed\n  heapSamples.push(used)\n\n  if (heapSamples.length > 10) {\n    const trend = heapSamples.slice(-10)\n    const growing = trend.every((v, i) => i === 0 || v >= trend[i-1])\n    if (growing) {\n      const growthMb = (trend.at(-1)! - trend[0]) \u002F 1024**2\n      console.warn(`[heap] steady growth: +${growthMb.toFixed(1)}MB over last 10 samples`)\n    }\n    heapSamples.splice(0, heapSamples.length - 10)\n  }\n}\n\nsetInterval(sampleHeap, 30_000)\n```\n\n---\n\n## Common leak patterns to fix\n\n```javascript\n\u002F\u002F Leak 1: event listener not removed\nconst handler = () => { \u002F* ... *\u002F }\nemitter.on('data', handler)\n\u002F\u002F Fix:\nemitter.once('data', handler)  \u002F\u002F or removeListener on cleanup\n\n\u002F\u002F Leak 2: setInterval not cleared\nconst id = setInterval(() => { \u002F* ... *\u002F }, 1000)\n\u002F\u002F Fix:\nprocess.on('exit', () => clearInterval(id))\n\n\u002F\u002F Leak 3: large object in closure\n\u002F\u002F function factory() { const big = new Array(1e6).fill(0); return () => big[0] }\n\u002F\u002F Fix: don't capture large objects in long-lived closures\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ heap snapshot in production → blocks event loop for 2-30 seconds\n❌ memwatch-next requires native build → fails on ARM without node-gyp\n❌ HeapDiff across async boundaries → GC between start and end confuses diff\n❌ process.memoryUsage().heapUsed alone → includes GC lag, not true live baseline\n❌ No threshold → leak detector fires on normal warmup growth\n❌ Listening to 'leak' but not acting → log fills, no remediation\n```\n","# \u002Fmemory-leak-detection\n\n## When to Use\n\n- Long-running agent sessions accumulating heap without releasing\n- Debugging why sandbox process is OOM-killed after hours of operation\n- Validating that event listeners and streams are properly cleaned up\n- Heap diffing to identify which objects grow between requests\n\n## Do NOT use for\n\n- One-shot scripts (leak only matters for long-running processes)\n- Production traffic interception (heap snapshots block the event loop)\n\n---\n\n## Heap leak detector (memwatch-next)\n\n```javascript\nimport memwatch from 'memwatch-next'\n\n\u002F\u002F 'leak' fires when heap grows 5 consecutive GC cycles\nmemwatch.on('leak', (info) => {\n  console.error('[memwatch] LEAK DETECTED', JSON.stringify(info))\n  \u002F\u002F info: { start, end, growth, reason }\n  \u002F\u002F growth is bytes added since last GC\n})\n\n\u002F\u002F GC stats after every garbage collection\nmemwatch.on('stats', (stats) => {\n  if (stats.current_base > 200 * 1024 * 1024) {  \u002F\u002F 200MB threshold\n    console.warn('[memwatch] heap baseline high:', Math.round(stats.current_base \u002F 1024**2), 'MB')\n  }\n})\n```\n\n---\n\n## Heap diff to find leaked objects\n\n```javascript\nimport memwatch from 'memwatch-next'\n\n\u002F\u002F Perform an action twice, diff heap to see what objects grew\nconst hd = new memwatch.HeapDiff()\n\n\u002F\u002F ... run the suspected leaky operation ...\nawait runAgentSession()\n\nconst diff = hd.end()\nconst growing = diff.change.details\n  .filter(d => d.size_bytes > 0)\n  .sort((a, b) => b.size_bytes - a.size_bytes)\n  .slice(0, 10)\n\nconsole.table(growing.map(d => ({\n  what:   d.what,\n  added:  d['+'],\n  freed:  d['-'],\n  deltaBytes: d.size_bytes,\n})))\n```\n\n---\n\n## V8 heap snapshot (built-in, no dependency)\n\n```javascript\nimport v8 from 'v8'\nimport { writeFileSync } from 'fs'\n\n\u002F\u002F Take a heap snapshot — blocks event loop, do offline\u002Fon-demand only\nfunction takeHeapSnapshot(path = `\u002Ftmp\u002Fheap-${Date.now()}.heapsnapshot`): string {\n  const snapshot = v8.writeHeapSnapshot(path)\n  console.log(`[heap] snapshot written: ${snapshot}`)\n  return snapshot\n  \u002F\u002F Open in Chrome DevTools → Memory tab → Load snapshot\n}\n```\n\n---\n\n## Simple heap trending (no library)\n\n```javascript\nconst heapSamples: number[] = []\n\nfunction sampleHeap(): void {\n  const used = process.memoryUsage().heapUsed\n  heapSamples.push(used)\n\n  if (heapSamples.length > 10) {\n    const trend = heapSamples.slice(-10)\n    const growing = trend.every((v, i) => i === 0 || v >= trend[i-1])\n    if (growing) {\n      const growthMb = (trend.at(-1)! - trend[0]) \u002F 1024**2\n      console.warn(`[heap] steady growth: +${growthMb.toFixed(1)}MB over last 10 samples`)\n    }\n    heapSamples.splice(0, heapSamples.length - 10)\n  }\n}\n\nsetInterval(sampleHeap, 30_000)\n```\n\n---\n\n## Common leak patterns to fix\n\n```javascript\n\u002F\u002F Leak 1: event listener not removed\nconst handler = () => { \u002F* ... *\u002F }\nemitter.on('data', handler)\n\u002F\u002F Fix:\nemitter.once('data', handler)  \u002F\u002F or removeListener on cleanup\n\n\u002F\u002F Leak 2: setInterval not cleared\nconst id = setInterval(() => { \u002F* ... *\u002F }, 1000)\n\u002F\u002F Fix:\nprocess.on('exit', () => clearInterval(id))\n\n\u002F\u002F Leak 3: large object in closure\n\u002F\u002F function factory() { const big = new Array(1e6).fill(0); return () => big[0] }\n\u002F\u002F Fix: don't capture large objects in long-lived closures\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ heap snapshot in production → blocks event loop for 2-30 seconds\n❌ memwatch-next requires native build → fails on ARM without node-gyp\n❌ HeapDiff across async boundaries → GC between start and end confuses diff\n❌ process.memoryUsage().heapUsed alone → includes GC lag, not true live baseline\n❌ No threshold → leak detector fires on normal warmup growth\n❌ Listening to 'leak' but not acting → log fills, no remediation\n```\n",{},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fmemory-leak-detection",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":7,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill memory-leak-detection",{"tool":39,"command":40},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill memory-leak-detection",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill memory-leak-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fmemory-leak-detection\u002FSKILL.md",true,[],[48,56,63,71,79,87],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]