More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Memory Growth & Resource Leaks

    1

    Repair Memory Growth & Resource Leaks is a bounded ToolForge Labs workflow.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Memory Growth & Resource Leaks

    Repair Memory Growth & Resource Leaks

    Example session with this skill installed

    A Node.js worker grows by roughly 200–300 MB during a long batch. It registers event listeners per job, keeps a retry timer, buffers some payloads, and uses one shared HTTP client. I have heap-summary excerpts and the worker code but no production profiler access. Find the likely retention paths and propose a bounded repair and repeatability test.

    • Read your context and instructions
    • Compiled the repair memory growth

    I would first separate JavaScript heap retention from sockets/buffers and other external memory, then map each resource to one owner and one teardown path. The strongest suspects from the supplied evidence are per-job listeners that are never removed, retry timers surviving terminal job states, and payload buffers retained by closures or retry state. I would make registration idempotent where ownership is process-wide, bind job-scoped listeners/timers to a disposable lifecycle, clear retained buffers at terminal transitions, and preserve the shared HTTP client rather than creating clients per job. A deterministic harness should run many synthetic jobs with forced success/failure/retry/cancellation, record listener/timer/handle counts after each batch, force GC only in the isolated test when available, and compare post-settle heap/external-memory plateaus. I would not claim a production leak is fixed until the supplied profiler/metrics confirm the same retention path.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Repair Memory Growth & Resource Leaks is a bounded ToolForge Labs workflow. Diagnose and repair application memory growth and resource leaks across caches, listeners, timers, buffers, queues, file/socket handles, background tasks, object retention, and shutdown cleanup. Works from repositories or partial heap/log/config evidence. Produces bounded repairs and deterministic leak tests while preserving performance and lifecycle policy. It works from a full repository or partial supplied evidence. The skill separates verified facts from assumptions, preserves existing product/security policy, avoids invented execution claims, and returns concrete repair or review steps with deterministic validation or explicit remaining gaps.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Cannot confirm leaks from single-point memory snapshots. Requires access to source code or specific profiler/log output for high-confidence diagnosis.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Use a clean branch or controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.

    Listed2 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill identifies the specific root causes of resource exhaustion, such as unclosed sockets or unbounded caches, and generates surgical code fixes and deterministic tests to ensure the leak is permanently resolved.

    It is optimized for high-concurrency environments including Node.js, Python, and Go, focusing on lifecycle gaps in background workers, event listeners, and API state management.

    To provide accurate repairs, you should provide the skill with relevant code snippets, repository access, or diagnostic artifacts like heap dump summaries and error logs.

    You receive the specialized agent logic for resource diagnosis, a suite of templates for generating leak-reproduction tests, and documentation on implementing bounded cache policies.

    While this skill excels at identifying logical ownership gaps and lifecycle failures, it does not perform real-time runtime profiling and requires external logs or reports to begin its analysis.

    New in LLM Ops