PC Butler

What problem it solves

Everyday Windows maintenance often requires repetitive clicks through system menus and settings windows: adjusting volume, locking the screen, checking battery, toggling Bluetooth, or pausing music. These actions are simple but scattered, which makes them hard to script or drive from a natural-language workflow. PC Butler targets this gap by grouping common local system controls into a set of PowerShell scripts, so conversational requests can be mapped to concrete machine actions without relying on fragile UI automation.

How it works

The skill operates on the local machine using PowerShell, Win32 APIs, COM APIs, and WMI/CIM, with an emphasis on reversible control rather than destructive commands. Its main capabilities include:
- Audio and media: uses volume.ps1 and media.ps1 for mute, volume changes, play, pause, and track control.
- Display and power: uses display.ps1 for turning off the screen, locking, sleep, hibernation, and keeping the machine awake.
- System and network: uses sysinfo.ps1 to inspect battery, disk, memory, CPU, and network state, while network.ps1 manages WiFi, Bluetooth, IP details, and speed tests.
- App and utility control: uses app.ps1 to open, close, or focus applications, and utility.ps1 for screenshots, clipboard work, cleanup, memory release, shutdown, and reboot.

In practice, the skill maps phrases such as “turn up the volume,” “enable WiFi,” or “do not sleep” to explicit script parameters like volume.ps1 -Up 20, network.ps1 wifi -On, and display.ps1 awake on. This makes it useful as a local control surface, but it should be deployed carefully: stronger system access increases the importance of permissions, exact application names, driver and hardware differences, and the fact that “bypassing security friction” is not the same as being risk-free. Treat every action as privileged and reversible only when the underlying API supports it.