Bilgisayar Mühendisi

    1

    Professional system engineer for diagnosing bottlenecks, cleaning dev bloat, and optimizing OS performance.

    $10

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Bilgisayar Mühendisi

    Example session with this skill installed

    My C: drive is almost full and the computer feels sluggish. I'm a dev working with Node and Docker. Can you find out what's eating the space and help me clean it up safely?

    • Read your context and instructions
    • Compiled the bilgisayar m hendisi

    I have completed a full diagnostic of your C: drive and system resources. The primary bottleneck is not your personal files, but a combination of developer caches and a ballooning WSL virtual disk.

    Diagnostic Summary

    The system is running with 92% disk utilization. While you suspected personal files, 65GB of the used space belongs to package caches and unused Docker layers.

    System Profile

    • Model: Dell XPS 15 9520
    • CPU: Intel i7-12700H (12% Idle)
    • RAM: 32GB (85% Used - WSL consuming 14GB)
    • Disk: 512GB NVMe SSD (42GB Free)

    Storage Breakdown

    ItemSizeDescriptionCategory
    Docker Images/Volumes28.5 GBUnused layers and dangling volumesKova 1 (Safe)
    node_modules18.2 GBSpread across 14 inactive projectsKova 3 (Structural)
    WSL (ext4.vhdx)14.0 GBVirtual disk hasn't shrunk after deletionsKova 2 (Setting)
    AppData/Local/Temp4.1 GBTemporary system and app filesKova 1 (Safe)
    OneDrive Cache12.5 GBLocal copies of cloud-only filesKova 2 (Setting)

    Recommended Actions

    • Prune Docker (Gain: ~28GB): Remove all dangling images and stopped containers.
    • Clear Temp Files (Gain: ~4GB): Safely wipe %TEMP% and browser caches.
    • WSL Memory Cap: I can create a .wslconfig to limit RAM usage to 8GB, preventing system sluggishness.

    Awaiting Decision

    Project Cleanup: I found 14 directories with node_modules that haven't been touched in 90 days. Should we move these to a _to_delete folder?
    *

    OneDrive Files-on-Demand: You have 12GB of files synced locally that are also in the cloud. We can switch these to "online-only."

    Next steps

    1. Would you like me to proceed with the Docker and Temp file cleanup now?
    2. Should I apply the RAM limit for WSL to stabilize your system performance?
    3. Do you want the list of inactive Node projects to review?

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

    What you get

    Reclaim disk space by purging hidden developer caches and Docker artifacts.Identify and resolve RAM bottlenecks caused by WSL or background tasks.Audit cloud storage sync issues that cause local disk exhaustion.Safely optimize Windows startup and system settings without breaking OS files.

    About this skill

    The problem

    Your machine is slowing down, the fan is constantly spinning, or you are getting "disk full" warnings, but you cannot pinpoint the actual source of the bloat. Generic cleaners often delete the wrong things or miss hidden developer artifacts that eat up gigabytes of space.

    What it does

    • Performs deep system diagnostics using PowerShell to identify CPU, RAM, and disk bottlenecks.
    • Scans for developer-specific bloat including node_modules, Docker images, WSL memory leaks, and package manager caches.
    • Differentiates between local storage exhaustion and cloud provider (OneDrive/iCloud) quota limits.
    • Categorizes findings into risk-based buckets: safe deletions, configuration tweaks, and structural changes.
    • Validates every action by measuring and reporting the exact storage or performance gain after optimization.

    Frameworks & tools

    Windows PowerShell, Desktop Commander, Docker, WSL, Node.js, OneDrive, macOS Terminal, and Linux shell environments.

    Why this beats prompting it yourself

    Standard prompts often guess or suggest risky "registry cleaners." This skill uses a "measure twice, cut once" engineering approach, running specific diagnostic scripts to find the root cause before suggesting a single deletion.

    Use cases

    • Clearing gigabytes of forgotten Docker layers and node_modules across projects.
    • Fixing high RAM usage caused by WSL or background startup processes.
    • Diagnosing whether a "disk full" error is actually a local issue or a cloud sync conflict.
    • Automating routine system hygiene without touching critical OS files.

    Known limitations

    Cannot modify protected system directories like WinSxS or System32. Restricted commands (like diskpart or netsh) require manual user intervention or specific cmdlet alternatives.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 24 days ago

    • Passed all security checks, Safe to install

    Needs access to

    Google

    Listed24 days ago

    What's inside

    Frequently Asked Questions