pc-healthcare

name: pc-healthcare description: End-to-end Windows PC health diagnostics for hardware and software incidents. Use when a user reports noise, vibration, instability, storage errors, thermal concerns, driver/device issues, or wants a full system health audit with evidence. Collect local evidence from event logs, WMI/CIM, storage telemetry, registry, and power settings; optionally validate hypotheses with internet sources; produce both a technical report and a plain-language report.

PC Healthcare

Use this skill to run structured Windows diagnostics and produce two outputs:

1. A technical report with evidence and source traceability.
2. A plain-language report for a non-technical user.

Read references/windows-data-sources.md before running commands. Read references/report-templates.md before writing final output.

Mandatory User Instruction

Before diagnostics, verify administrator rights.

If Codex is not running as Administrator, stop and instruct the user to relaunch Codex in PowerShell with "Run as Administrator".

State explicitly:

• Administrator access is mandatory for this skill.
• Without it, sensor, registry, and some hardware/telemetry data can be incomplete or inaccessible.

Check command:

([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(
  [Security.Principal.WindowsBuiltInRole]::Administrator
)

Before creating report files, explicitly ask the user where to save:

• Technical report file path.
• Plain-language report file path.

Do not choose output paths implicitly.

Execute This Workflow

1. Confirm scope and symptom pattern.
2. Verify Administrator mode and instruct user if missing.
3. Collect baseline machine and OS context.
4. Collect storage health, disk mapping, and file-system status.
5. Collect sensor and thermal data from all available providers.
6. Collect software, driver, and device error state.
7. Collect power policy and registry settings that can explain intermittent behavior.
8. Build a timestamped event timeline and correlate with symptoms.
9. Validate likely causes with internet sources when needed.
10. Ask user for output paths for both report files.
11. Produce technical and plain-language reports.

Keep Diagnostics Safe

• Run read-only diagnostics only.
• Do not execute any write/repair/change operation.
• Do not modify registry, power settings, drivers, or disk structures.
• Do not run repair/fix commands (/f, /r, repair mode, registry writes, service config writes).
• Separate "filesystem integrity is clean" from "physical media is healthy".
• Write is allowed only for:
  • The two user-approved report files.
  • Temporary files inside a tmp folder if intermediate copy/merge steps are required.
• Do not write anywhere else.

Evidence Standard

For every conclusion, include:

• Source type (event log, WMI/CIM, registry, sensor, internet).
• Exact command or query.
• Timestamp.
• Key output fields used for the conclusion.

If evidence is missing or conflicting, say so explicitly and lower confidence.

Correlation Rules

• Map \\Device\\HarddiskX\\DRY events to real disks before concluding.
• Distinguish internal disks from removable USB media.
• Separate one-off events from repeating patterns.
• Use absolute dates in reports.

Internet Use Rules

Use internet checks when:

• The user asks for current recommendations or pricing.
• A diagnosis depends on up-to-date vendor advisories or known-issue bulletins.
• You need a source-backed explanation for a specific event ID or device behavior.

Prefer primary documentation and vendor pages. Include URLs and retrieval date.

Output Requirement

Always deliver both sections:

1. Technical report (for engineering/repair decisions).
2. Plain-language report (for non-technical user).

Use templates in references/report-templates.md.