Computer health check
Skill yigityildiz0/universal-ai-skill-library/skills/common/computer-health-check
531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.
npx -y skills add yigityildiz0/universal-ai-skill-library --skill computer-health-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Perform a bounded, read-only health check of a Windows, macOS, or Linux computer, covering storage, memory pressure, CPU activity, startup load, battery where available, updates, and obvious errors. Use when asked to check PC health, diagnose a slow computer, inspect disk/RAM/CPU, or summarize system condition; request approval before any cleanup, install, update, or configuration change.
SKILL.md
1.9 KB, 309 tokens by cl100k_base, as published. Nobody here has run it
Computer Health Check
Diagnose first; do not repair by default.
Scope and safety
Confirm the operating system and whether commands may run locally. Start with non-destructive inspection only. Never delete files, disable startup items, install updates, change drivers, or alter settings during the health check.
Workflow
- Collect a bounded snapshot of uptime, CPU load, memory pressure, storage free space and errors, top active processes, startup load, battery health when present, and recent system/application errors.
- Use OS-appropriate measurements. On Windows, calculate CPU utilization from two time-separated samples or a performance counter; do not present cumulative process CPU time as a percentage.
- Treat unavailable sensors and unknown SMART/physical-disk status as unknown, not a failure.
- Separate observations, likely causes, confidence, and safe next checks.
- Prioritize at most five actions by impact and risk. Offer cleanup or change steps only as separate, opt-in actions with expected impact and rollback.
Output
Snapshot and coverage
Findings: evidence | likely cause | confidence
Healthy / watch / investigate areas
Top 3–5 next actions
What was not checked and why
Guardrails
- Do not run network update checks, package upgrades, malware scans, or cleanup without explicit permission.
- Avoid a misleading single health score; report uncertainty instead.
- Redact user names, paths, serials, product keys, and process arguments when they are not needed.