agentleFS
Sign inStart free
Indium-AI-LabsIndium-AI-Labs/indium-agentkit/skills/memory-leak-investigation/SKILL.md

memory-leak-investigation

Skill18 starsChanged 2 months agoNo licenceView on GitHub

Find and fix memory leaks and unbounded growth in long-running Node.js, Python, JVM, or Go processes: confirm a real leak, reproduce it with a repeatable load loop, compare heap snapshots or profiles to find the retainer, fix or bound it, and prove the fix with a growth test. Use when memory climbs until OOM kills or restarts, heap after GC rises under steady load, or goroutines or tasks pile up. Not for slow code without growth (use the performance-optimization skill).

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free