linux-diag

Generate structured Linux diagnostic plans for CPU, memory, disk, and network issues.

1|1|Updated Nov 1, 2015
One-click install
npx skills add https://github.com/s4kr4/dotfiles --skill linux-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-diag
Source: https://github.com/s4kr4/dotfiles/tree/main/.claude/skills/linux-diag
Command: npx skills add https://github.com/s4kr4/dotfiles --skill linux-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Linux system problems such as slow performance, unresponsiveness, or unexpected errors are common and often require methodical investigation. This Skill provides a structured knowledge base with diagnostic steps and reference material to guide users through CPU, memory, disk, network, process, service, log, GPU/NVIDIA, graphics (xrdp), and Docker/container issues.

Core Features & Use Cases

  • Comprehensive diagnostic categories with practical commands to identify root causes.
  • Flowcharts and reference material to guide step-by-step troubleshooting.
  • Use Case: When a Linux server slows down, follow the CPU, memory, disk, network, and service checks to isolate bottlenecks and plan remediation.

Quick Start

Start with baseline checks: uptime, free -h, df -h, top -b -n1, dmesg | tail -30, and journalctl -p err -n 20 to surface immediate issues; then consult the referenced COMMANDS.md and FLOWCHART.md for deeper diagnostics.

Frequently Asked Questions about linux-diag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why my Linux server is running slow?

Diagnose Linux performance issues by running baseline commands: uptime, free -h, df -h, top -b -n1, dmesg | tail -30, and journalctl -p err -n 20 to identify CPU, memory, disk, or service bottlenecks. Then consult structured flowcharts and diagnostic commands for CPU, memory, disk, network, and process analysis to isolate root causes.

What Linux commands should I use to troubleshoot unresponsiveness?

Use structured diagnostics across CPU (top, mpstat), memory (free, vmstat), disk (df, iostat), network (netstat, ss), processes (ps, lsof), services (systemctl status, journalctl), and GPU/container metrics to methodically identify which subsystem is unresponsive. The Skill codifies these commands into an actionable step-by-step plan.

Can I use this to diagnose Docker container and GPU issues on Linux?

Yes. The Skill covers diagnostics for Docker containers, NVIDIA GPU, and graphics (xrdp) performance alongside traditional CPU, memory, disk, network, and service checks. It provides commands and flowcharts tailored to container and GPU troubleshooting scenarios.

How do I systematically troubleshoot Linux errors without guessing?

Follow the Skill's structured flowcharts and reference commands across eight diagnostic categories—CPU, memory, disk, network, processes, services, logs, and GPU/graphics. Each category contains methodical checks to surface immediate issues and guide deeper investigation to identify error sources safely.

What should I check first when a Linux system reports errors?

Start with quick baseline checks: uptime, free -h, df -h, top -b -n1, dmesg | tail -30, and journalctl -p err -n 20 to surface immediate errors and resource constraints. These reveal whether issues stem from CPU, memory, disk saturation, or service failures before deeper diagnostics.

Does this cover network and service diagnostics for Linux troubleshooting?

Yes. The Skill includes structured diagnostics for network connectivity and service health alongside CPU, memory, disk, and process checks. It provides commands and flowcharts to isolate network bottlenecks and service failures contributing to slowdowns or errors.