optimize

windows-pc-optimizer

A Claude Code skill that acts as a systematic Windows PC optimization consultant. It diagnoses your specific system first, builds a custom plan based on your use case, and executes it with your approval — without assuming what software you run or how you use your machine.

---

⚠️ Security and risk warnings

Read this before installing.

This skill operates with Administrator privileges and can modify core system settings, disable services, remove software, and change registry keys. That is by design — deep optimization requires deep access. But you should understand the implications:

What this means in practice

• An LLM is making decisions about your system. It reads diagnostic output, reasons about what to change, and executes PowerShell scripts as Administrator. It is not a deterministic script — it makes judgment calls.

• Mistakes are possible. The skill is designed to be conservative and ask for approval before acting, but LLMs can misread output, make wrong inferences, or generate code with bugs. Always review the proposed plan before approving.

• Some changes are not easily reversible. Uninstalling software, removing startup items, and changing services can break things that are hard to restore without knowing exactly what was changed. This is why the skill creates a restore point and registry backups first — but those are not a guarantee.

• The skill does not have access to your files or personal data beyond what diagnostic scripts explicitly collect (process names, installed software names, folder sizes). It does not read documents, emails, or credentials.

How risk is mitigated

1. System Restore Point is created before any changes.
2. Registry is backed up (Run keys, Services) before any modifications.
3. Plan is proposed and requires explicit approval before execution.
4. Logs are written to a timestamped directory so you can see exactly what ran.
5. Use case is captured upfront — audio production stacks, dev tools, and critical hardware are explicitly protected.

When NOT to use this skill

• On a production server or work machine where downtime is unacceptable
• If you don't have a backup of important files
• If you're not comfortable with PowerShell and Windows system administration in general
• If you need guaranteed stability above all else (e.g., studio session tomorrow)

In those cases: make a backup first, then run it on a day where you can afford a few hours of troubleshooting if something goes wrong.

---

What it does

The skill follows a 6-phase workflow:

Phase	What happens
0 — Safety	Restore point + registry backup + baseline snapshot
1 — Interview	Captures your use case and what must be preserved
2 — Diagnosis	Full system scan (hardware, disk, RAM, startup, services, drivers)
3 — Analysis	Builds a custom optimization plan for your specific profile
4 — Proposal	Presents the complete plan — nothing runs until you approve
5 — Execution	Runs approved steps with logging and checkpoints
6 — Report	Before/after benchmark, pending manual actions documented

What it optimizes

• Disk space — temp files, caches, driver leftovers, WinSxS, browser caches, dev artifact caches (npm, pip, cargo, etc.)
• RAM at idle — startup items that don't need to run at boot, services set to Auto that should be Manual
• Boot time — startup entry reduction
• Gaming performance — MPO off, MSI Mode, HAGS, FSE mode, Ultimate Performance power plan, timer resolution, network latency
• Audio production — timer resolution, USB suspend, fast startup off, protecting audio interface drivers
• Driver health — flags outdated GPU drivers, missing chipset drivers, RAM running below rated speed (XMP/DOCP)
• Privacy/telemetry — Windows telemetry, Game DVR, advertising ID, WER

What it never does without confirmation

• Remove or uninstall specific games, software, or plugins
• Move audio library content (samples, instruments)
• Change BIOS settings (those require manual steps)
• Disable security software (Defender, firewall)
• Touch audio interface drivers or iLok/PACE license services

---

Installation

Requirements

• Windows 10 or Windows 11
• Claude Code installed
• PowerShell 5.1+ (built into Windows 10/11)
• A secondary drive is recommended for logs — the scripts will use C: if none is available

Step 1 — Clone the repo

git clone https://github.com/YOUR_USERNAME/windows-pc-optimizer

Step 2 — Add the marketplace

In Claude Code, run:

/plugin marketplace add C:\path\to\windows-pc-optimizer

Example:

/plugin marketplace add C:\Users\YourName\Documents\windows-pc-optimizer

You should see: Successfully added marketplace: windows-pc-optimizer

Step 3 — Install the plugin