About this skill

Problem

When diagnosing a slow computer, useful signals are scattered across shell commands, system settings, and ad hoc scripts: CPU, memory, disk, battery, and suspicious processes often require separate checks. The commands also differ across macOS, Windows, and Linux. computer-efficiency-skill turns that routine read-only inspection into a repeatable workflow that reports state first and gives scoring or recommendations later.

How it works

It detects the OS and runs platform-specific commands. On macOS it uses top -l 1, vm_stat, df -h, pmset -g batt, and ps aux; on Windows PowerShell it uses Get-Counter, Get-WmiObject Win32_OperatingSystem, Get-WmiObject Win32_LogicalDisk, Get-WmiObject Win32_Battery, and Get-Process; on Linux it uses top -bn1, free -m, df -h, /sys/class/power_supply/, and ps aux. It then calculates a 100-point score: CPU load at 20%, free memory at 25%, battery state at 15%, and process health at 10%, producing a health report or cleanup suggestions. Report generation relies on qclaw-text-file, and scheduled runs can use qclaw-cron-skill. The safety rules are explicit: read-only scans, listing items, and generating reports may run automatically, but deleting files, killing processes, changing system configuration, or emptying the Trash requires explicit confirmation such as “confirm”, “execute”, or “agree”.

Boundaries

It is useful as a quick snapshot for personal machines, dev boxes, or first-line ops checks, but it does not replace professional monitoring, alerting, log analysis, or compliance auditing. When red-line thresholds are hit—high CPU, high memory usage, low disk space, or low battery—verify the responsible processes and workload impact. Results may be incomplete if the environment lacks permissions, battery metadata, or WMI components.

Screenshots

Use Cases

After taking over a colleague’s machine, inspect CPU, memory, disk, and battery state to find the slowdown cause.
During dev machine checks, aggregate read-only metrics and generate a health report with a 100-point score.
When suspicious processes consume resources, list process and memory usage and get actionable cleanup suggestions.
Periodically check backup workstations to confirm disk free space and battery level do not hit red thresholds.

Best For

IT operations engineers supporting multiple endpoints who need consistent read-only triage across macOS, Windows, and Linux.
Engineers running builds or modeling locally who want to check whether CPU, memory, and disk are near bottlenecks.
Technicians taking over older laptops or test machines who need a quick health report and cleanup suggestions.
Technical leads managing dev cloud desktops or shared workstations who need threshold checks and audit notes.