Skip to content
Back to search

desktopdiag

MarketplaceWorks with Claude CodeGitHub

DesktopDiag: a read-only Windows PC health check skill for Claude Code, with French and English reports.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Lykroze9/DesktopDiag with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Lykroze9/DesktopDiag'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lykroze9--desktopdiag/badge.svg)](/listings/lykroze9--desktopdiag)

HTML

<a href="/listings/lykroze9--desktopdiag"><img src="/api/listings/lykroze9--desktopdiag/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

As a Claude Code plugin

/plugin marketplace add Lykroze9/DesktopDiag
/plugin install desktopdiag@desktopdiag

As a standalone skill

Copy `skills/desktopdiag` to `%USERPROFILE%\.claude\skills\desktopdiag` (all projects) or to `.claude\skills\desktopdiag` in a project.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "desktopdiag",
  3. "owner": {
  4. "name": "Lykroze"
  5. },
  6. "description": "DesktopDiag: a read-only Windows PC health check skill for Claude Code, with French and English reports.",
  7. "plugins": [
  8. {
  9. "name": "desktopdiag",
  10. "source": "./",
  11. "description": "Read-only Windows PC health check: crashes/BSOD, GPU resets, SSD wear, hardware errors, boot time, CPU throttling, security. French and English reports."
  12. }
  13. ]
  14. }
README.md · README · 121 lines
  1. # DesktopDiag
  2. ### Is your PC slow, glitchy, crashing... or do you just want a quick checkup?
  3. DesktopDiag scans your Windows PC and tells you in plain words what's wrong, and what to do about it.
  4. > **👋 A personal side project.** DesktopDiag started as a custom tool I built for my own PC, after
  5. > chasing GPU freezes and blue screens, and grew into a skill I wanted to share. It is not a
  6. > commercial product and it is far from finished.
  7. >
  8. > **Your feedback is very welcome!** Tried it? Found a bug, a wrong diagnosis, a missing check, or
  9. > just have an idea? Please [open an issue](https://github.com/Lykroze9/DesktopDiag/issues) or start a
  10. > [discussion](https://github.com/Lykroze9/DesktopDiag/discussions), in English or French. Every comment helps make the skill better.
  11. **Read-only Windows PC health check for Claude Code.** Ask "check my PC" or describe a problem
  12. ("my screen goes black in games", "random reboots") and Claude collects the data, explains it in
  13. plain language, scores your PC and tells you what to do next. Reports in **English or French**.
  14. [🇫🇷 Version française](README.fr.md)
  15. ## What it checks
  16. | Area | Details |
  17. |---|---|
  18. | Stability | Blue screens (stop code + parameters), unexpected shutdowns, crash dumps, Windows reliability index |
  19. | Graphics | Display driver resets (TDR), NVIDIA/AMD/Intel driver errors, driver version and age, overclocking tools at startup |
  20. | Storage | Free space, disk health, SSD wear/temperature/errors (SMART via smartctl), disk errors mapped to the right drive (USB vs system SSD) |
  21. | Hardware | WHEA hardware errors (CPU, RAM, PCIe), Windows Memory Diagnostic result, TPM errors, devices in error (code 10/43...) |
  22. | Security | Antivirus status, firewall profiles, last successful Windows Update and recent failures, pending reboot, UAC, Secure Boot |
  23. | Performance | Real CPU % (sampled, not cumulative), RAM and commit usage, top processes |
  24. | Boot time | Firmware/BIOS time of each boot, Fast Startup; with admin: total boot time and what slowed each boot down (app, driver, service) |
  25. | Heat | CPU throttling by firmware (heat or power limits), live performance limit, thermal zones when the PC exposes them |
  26. | Network | Wi-Fi signal, router ping, DNS response time, Wi-Fi and Ethernet drops |
  27. | Battery | Laptops: health (current vs original capacity) and charge cycles |
  28. | Maintenance | Startup entries, temp folders, uptime, page file and hibernation file size |
  29. | History | Every check is saved locally and compared with the previous one: new crashes since last time, space lost, driver/BIOS updates, startup entries added |
  30. | Follow-up | After each report, Claude proposes the next check sized to what it found (in 2-4 days after a fix, weekly while problems settle, monthly otherwise) and schedules it on your OK with the Claude desktop app's local scheduled tasks |
  31. ## Why another one?
  32. Existing Windows diagnostic skills/MCP servers skip the problems people actually hit: GPU driver
  33. resets, NVMe wear, BSOD culprit drivers, and "did it get better since last week?". DesktopDiag
  34. also:
  35. - runs on the **built-in Windows PowerShell 5.1** (no PowerShell 7, Node or Python needed), Windows 10 and 11;
  36. - needs **no admin** for the main check; an optional admin step adds SMART, dump analysis and a read-only file system scan;
  37. - is **read-only**: fixes are proposed with risk levels and run only after your explicit OK;
  38. - documents real-world traps (inflated crash counts in the Application log, `chkdsk` access denied, vendor utilities reinstalling drivers, sandboxed registry writes...);
  39. - has a **share mode** that strips user name, computer name and paths for forum posts.
  40. ## Install
  41. ### As a Claude Code plugin
  42. ```
  43. /plugin marketplace add Lykroze9/DesktopDiag
  44. /plugin install desktopdiag@desktopdiag
  45. ```
  46. ### As a standalone skill
  47. Copy `skills/desktopdiag` to `%USERPROFILE%\.claude\skills\desktopdiag` (all projects) or to
  48. `.claude\skills\desktopdiag` in a project.
  49. ## Use
  50. Just talk to Claude Code:
  51. - "Check my PC" / "Is my PC healthy?"
  52. - "My screen goes black for a few seconds when I play"
  53. - "My PC rebooted by itself twice this week"
  54. - "Is my SSD OK?"
  55. - "Do a full check" (proposes the admin deep scan)
  56. - "Make a shareable report for a forum"
  57. - "Schedule a check every month" / "Check again in 4 days"
  58. You can also run the collector yourself:
  59. ```powershell
  60. powershell -NoProfile -ExecutionPolicy Bypass -File skills\desktopdiag\scripts\collect.ps1
  61. powershell -NoProfile -ExecutionPolicy Bypass -File skills\desktopdiag\scripts\compare.ps1
  62. ```
  63. Add `-Summary` to `collect.ps1` for a compact digest (about 10x smaller than the full snapshot).
  64. Claude uses it by default, so each check costs far fewer tokens.
  65. Snapshots are stored in `%LOCALAPPDATA%\DesktopDiag\history`.
  66. ## Score
  67. The score and the area levels come from `skills/desktopdiag/rules/rules.json`, applied by
  68. `scripts/score.ps1`: the same PC always gets the same score, and Claude adds the explanations.
  69. Thresholds are documented in [rules/README.md](skills/desktopdiag/rules/README.md).
  70. ## Development
  71. ```powershell
  72. powershell -NoProfile -ExecutionPolicy Bypass -File tests\run-tests.ps1 -Live
  73. ```
  74. Tests use synthetic snapshots (`tests/fixtures.ps1`, no real machine data) and run on every push
  75. with GitHub Actions, together with PSScriptAnalyzer. See [CHANGELOG.md](CHANGELOG.md) for what changed.
  76. ## Optional tools
  77. - [smartmontools](https://www.smartmontools.org/) (`winget install smartmontools.smartmontools`) for detailed SSD/HDD SMART data.
  78. - WinDbg (`winget install Microsoft.WinDbg`) to identify the driver behind a blue screen. The first analysis downloads public symbols from Microsoft.
  79. ## Privacy
  80. Everything runs locally. Nothing is uploaded (except Microsoft symbol downloads if you accept dump
  81. analysis). Disk serial numbers are hashed. Use share mode before posting a report anywhere.
  82. ## Disclaimer
  83. DesktopDiag reads system information and gives advice. It does not replace a technician. Hardware
  84. interventions (BIOS updates, repasting, part replacement) are your decision and responsibility.
  85. ## License
  86. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.