diagnosing-mac-performance

To diagnose a slow Mac, this Skill collects CPU, memory, and I/O snapshots using built-in macOS tools like top and ps. It then identifies bottlenecks and surfaces top resource consumers so you can take targeted remediation action instead of guessing.

High memory pressure on macOS is caused by runaway processes or heavy app usage exhausting available RAM. This Skill uses the memory_pressure utility and sysctl to collect system metrics, identifying the specific daemons or applications creating the bottleneck.

Yes, you can troubleshoot CPU bottlenecks using built-in macOS command-line tools. This Skill runs system commands like ps and top to gather process data, identifying runaway daemons and high CPU consumers to deliver a structured diagnostic report.

No special software dependencies are required. This Skill relies entirely on built-in macOS utilities such as ps, top, sysctl, and memory_pressure to collect system snapshots and process data for identifying performance bottlenecks.

The best way to identify top resource consumers is a structured diagnostic workflow that collects parallel CPU and memory metrics. This Skill gathers process data across development and personal use contexts to surface culprits and recommend remediation steps.

You should run a diagnostic when slow Mac performance persists or involves heavy app usage and memory pressure. By collecting system snapshots before restarting, this Skill identifies specific runaway processes, providing actionable remediation guidance rather than a temporary fix.