360-degree Windows system health diagnostics — covers CPU, memory, disk, network, security, startup programs, services, system info, hardware, and installed software. Use this skill whenever the user mentions system diagnostics, PC health check, performance issues, 'why is my computer slow', disk space, memory usage, startup optimization, security audit, bloatware removal, system cleanup, laptop health, or wants to keep their PC in prime condition. Also use when the user asks about high CPU, RAM usage, what's eating their disk, or wants a full system report.
Performs a comprehensive system health check across 10 categories, generates a severity-classified HTML report, and summarizes findings with actionable recommendations.
Run the PowerShell collection script. It gathers data across all 10 diagnostic categories and outputs JSON:
powershell -NoProfile -ExecutionPolicy Bypass -File "C:/Users/simon/.claude/skills/windows-diagnostics/scripts/collect_diagnostics.ps1"
The script outputs JSON to stdout and saves it to %TEMP%\windows_diagnostics.json. Each section has its own error handling — if one category fails (e.g., Defender status requires admin), the rest still complete.
python "C:/Users/simon/.claude/skills/windows-diagnostics/scripts/generate_report.py"
This reads the JSON, applies severity rules, and produces a styled HTML report at ./SystemHealthReport_YYYY-MM-DD.html (in the current working directory). It also prints a summary to stdout.
Optionally specify a custom output path:
python "C:/Users/simon/.claude/skills/windows-diagnostics/scripts/generate_report.py" "/path/to/report.html"
After both scripts run, present findings to the user organized by severity:
For each finding, include the recommendation. Be specific and actionable.
Based on findings, offer to help with:
Get-AppxPackage -Name "..." | Remove-AppxPackage)The script works without admin, but these features require elevation:
If key sections show errors, tell the user: "Some security checks require administrator privileges. Would you like me to explain how to re-run elevated?"
To re-run elevated, the user should open an admin terminal and run the same commands.
Read references/severity_rules.md for the full classification rules. Key thresholds:
Read references/known_bloatware.md for the list of common pre-installed packages that can be safely removed, and which packages must NOT be removed.
node_modules, .git, and .venv directories.Win32_Product class is intentionally NOT used (it triggers MSI reconfiguration and is extremely slow). Software is enumerated from the registry instead.