computer-diagnosis

Stars8

Forks2

UpdatedJuly 31, 2026 at 13:26

Comprehensive computer diagnosis and troubleshooting. Use this skill when a user reports issues with their computer (e.g., "my computer is slow", "it's freezing", "loud fan noise", "no disk space") to analyze system metrics (CPU, RAM, Disk, Network) across macOS, Windows, and Linux, and generate a detailed report with actionable recommendations.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

fritzprix

fritzprix/libr-agent

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

6 files

SKILL.md

readonly

name	computer-diagnosis
description	Comprehensive computer diagnosis and troubleshooting. Use this skill when a user reports issues with their computer (e.g., "my computer is slow", "it's freezing", "loud fan noise", "no disk space") to analyze system metrics (CPU, RAM, Disk, Network) across macOS, Windows, and Linux, and generate a detailed report with actionable recommendations.

Computer Diagnosis Skill

This skill allows Claude to act as a technical support assistant. It gathers system information using Python's psutil library (making it cross-platform), analyzes the metrics for common issues, and provides a structured report.

Path conventions

Paths in this skill are relative to the directory containing this SKILL.md, not to the workspace root or the shell's current ./.

Scripts in this skill use paths like scripts/...
Reference material in this skill uses paths like references/... and assets/...
When a command below says python scripts/..., resolve that script path against the skill's absolute Base Directory
In command examples below, replace <skill-base-dir> with the skill's actual absolute Base Directory
Files created in the examples are workspace files unless the instruction explicitly says otherwise

Workflow

Information Gathering: When a user reports an issue, execute the data collection script to snapshot the current system state.
```
python "<skill-base-dir>/scripts/collect_info.py" > sys_info.json
```
Data Analysis: Use the analysis script to parse the collected JSON and identify critical issues (high CPU/Memory, full disks).
```
python "<skill-base-dir>/scripts/analyze_info.py" sys_info.json > analysis_result.json
```
Report Generation: Read both sys_info.json and analysis_result.json. Present the findings to the user using the template found in assets/report_template.md.

Reference Materials

Symptoms Guide: See references/symptoms.md to map user descriptions to specific metrics.

Notes

The scripts rely on psutil. If it's missing, you may need to install it (pip install psutil).
Ensure you have permission to read system states. Some disk partitions or network interfaces might throw PermissionError, which the script handles by skipping them.
Always provide actionable recommendations alongside the raw data. Users want to know how to fix the problem.

More from this repository

same repository

feature-refactor-proposal

fritzprix/libr-agent

Analyze codebase against new feature requirements, map affected modules and dependencies, identify architectural risks, and propose a structured refactoring and implementation plan before writing code. Use when starting a new feature, planning refactoring, analyzing codebase impact, or reviewing feature feasibility.

2026-08-028

create-pr

fritzprix/libr-agent

Create a GitHub pull request with gh, target the correct base branch, push only committed work, and bind related issues via Fixes/Closes keywords. Use when asked to create a PR, open a pull request, push and open PR, link/bind/associate an issue to a PR, add Fixes #N, or close issues on merge.

2026-08-018

review-local-changes

fritzprix/libr-agent

Comprehensive review and audit of uncommitted local code changes in git working copy (staged, unstaged, untracked). Use when asked to review local changes, audit git diff, check uncommitted work before commit/PR/push, or inspect working copy edits for potential bugs, security issues, formatting, or regression risks.

2026-08-018

harbor-harness-improvement-loop

fritzprix/libr-agent

Analyze Harbor benchmark jobs and ATIF trajectories, identify evidence-backed weaknesses across LibrAgent builtin tools, prompts, agent guidance, execution policy, and benchmark instrumentation, then design controlled improvements and rerun comparisons. Use when analyzing Harbor or Terminal-Bench results, optimizing the harness, investigating tool-call failures or retries, auditing prompt/context efficiency, or running repeated BM → analysis → improvement cycles.

2026-07-318

soul-awakening

fritzprix/libr-agent

Re-anchor an AI agent to its SOUL.md persona by re-internalizing tone, rules, and identity. Use when the agent drifts into generic/corporate responses, is explicitly asked to reconnect with its soul, or needs to bootstrap a missing SOUL.md. SOUL content is already injected into the system prompt as

2026-07-318

soul-awakening

fritzprix/libr-agent

Re-anchor an AI agent to its `SOUL.md` persona by locating the active soul file, reading it, and re-internalizing its tone, rules, and identity. Use when the agent is starting fresh, drifting into generic/corporate responses, explicitly asked to read its soul, or needs to resync with the dedicated persona layer loaded from `.github/SOUL.md`, `SOUL.md`, or lowercase variants.

2026-07-318

name	computer-diagnosis
description	Comprehensive computer diagnosis and troubleshooting. Use this skill when a user reports issues with their computer (e.g., "my computer is slow", "it's freezing", "loud fan noise", "no disk space") to analyze system metrics (CPU, RAM, Disk, Network) across macOS, Windows, and Linux, and generate a detailed report with actionable recommendations.

Computer Diagnosis Skill

Path conventions

Paths in this skill are relative to the directory containing this SKILL.md, not to the workspace root or the shell's current ./.

Scripts in this skill use paths like scripts/...
Reference material in this skill uses paths like references/... and assets/...
When a command below says python scripts/..., resolve that script path against the skill's absolute Base Directory
In command examples below, replace <skill-base-dir> with the skill's actual absolute Base Directory
Files created in the examples are workspace files unless the instruction explicitly says otherwise

Workflow

Information Gathering: When a user reports an issue, execute the data collection script to snapshot the current system state.
```
python "<skill-base-dir>/scripts/collect_info.py" > sys_info.json
```
Data Analysis: Use the analysis script to parse the collected JSON and identify critical issues (high CPU/Memory, full disks).
```
python "<skill-base-dir>/scripts/analyze_info.py" sys_info.json > analysis_result.json
```
Report Generation: Read both sys_info.json and analysis_result.json. Present the findings to the user using the template found in assets/report_template.md.

Reference Materials

Symptoms Guide: See references/symptoms.md to map user descriptions to specific metrics.

Notes

The scripts rely on psutil. If it's missing, you may need to install it (pip install psutil).
Ensure you have permission to read system states. Some disk partitions or network interfaces might throw PermissionError, which the script handles by skipping them.
Always provide actionable recommendations alongside the raw data. Users want to know how to fix the problem.