菜单
Local Linux lag and performance diagnosis. Run read-only probes based on the user's symptoms to find CPU, memory, disk, or local network bottlenecks, then give safe advice. Never auto-remediate. Also matches Chinese requests such as 系统卡顿、机器好慢、内存不足、突然重启、OOM、磁盘很慢.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AI-Shell-Team/aish --skill diagnose-system-lag命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | diagnose_system_lag |
| version | 3.0.0 |
| description | Local Linux lag and performance diagnosis. Run read-only probes based on the user's symptoms to find CPU, memory, disk, or local network bottlenecks, then give safe advice. Never auto-remediate. Also matches Chinese requests such as 系统卡顿、机器好慢、内存不足、突然重启、OOM、磁盘很慢. |
| author | aish |
| context | subagent |
| agent | troubleshoot |
| allowed-tools | ["bash","read_file","grep","glob"] |
| triggers | ["diagnose_system_lag","system lag diagnosis","performance check","system is slow","high load","out of memory","OOM","disk is slow","unexpected reboot","系统卡顿诊断","看看系统卡不卡","系统很卡","机器好慢","内存不足","磁盘很慢","突然重启","异常关机"] |
| platforms | ["linux"] |
| distributions | ["deepin","debian","ubuntu","uos"] |
Short-path, read-only diagnosis for lag, slowness, resource pressure, or a recent unexpected reboot on this host.
Out of scope: full sos collection, long-running health baselines, cloud VPC troubleshooting, auto config changes or killing processes. Use sosreport-analyzer, deepin-sysassist, or other skills for those.
scripts/diagnose.sh).Understand symptom → quick check (only if vague) → focused probes → answer
↑ stop when evidence is enough ↑
| User report | Focus | First step |
|---|---|---|
| Slow / high load / no specifics | Unknown | Quick check |
| Low memory, Swap, OOM, process killed | Memory | Memory probes |
| Copy/open large files stalls, disk noise, frozen I/O | Disk | Disk probes |
| High CPU, fans spinning, one process pegged | CPU | CPU probes |
| Slow/unreachable network (local host side) | Network | Local network probes |
| Sudden reboot, black screen then recovery, unclean shutdown | Incident | Reboot/crash probes |
Named apps (browser, WPS, Java, a service) are suspects under the matching focus—not a separate workflow.
nproc
uptime
free -h
df -h
vmstat 1 5
ps -eo pid,ppid,comm,%cpu,%mem,state --sort=-%cpu | head -15
ps -eo pid,ppid,comm,%cpu,%mem,state --sort=-%mem | head -15
Then decide:
| Observation | Next |
|---|---|
| Very low available memory or clearly rising Swap | Memory probes |
Sustained high wa in vmstat, or many D state processes | Disk probes |
| Load clearly above CPU count and idle is very low | CPU probes |
High load with high idle and high wa | Prefer disk, not CPU |
| Root or home ≥ 90% | Call out disk-full risk; inspect large dirs only if needed |
| All looks normal | Conclude no clear bottleneck; ask when/how it reproduces |
Add only the set that fills the current gap. If a tool is missing, skip it and note the fallback in the answer.
free -h
swapon --show
ps -eo pid,user,comm,rss,%mem --sort=-rss | head -20
journalctl -k -b --no-pager | grep -iE 'out of memory|oom|killed process' | tail -30
If still missing “who was killed / cache vs anon”:
grep -E 'MemTotal|MemAvailable|Buffers|Cached|AnonPages|Shmem|SwapTotal|SwapFree' /proc/meminfo
df -h /dev/shm /run /tmp
vmstat 1 5
iostat -xz 1 5
df -h
ps -eo pid,state,comm,wchan:32 | awk '$2=="D" || $2=="d"' | head -20
Skip iostat if missing and note that in Evidence. If still missing “who is writing” and the tool exists: pidstat -d 1 5 or iotop -boPqqq -n 3.
nproc; uptime
vmstat 1 5
ps -eo pid,user,comm,state,%cpu,%mem --sort=-%cpu | head -20
If still missing “what it waits on”, for a suspect PID: cat /proc/<pid>/wchan.
ip -s link
ss -s
ss -tnp | head -30
Inspect local sockets and error/retransmit counters first. For full path quality to a remote target, prefer network-path-diagnose.
Start with last -x. Prefer specific signatures (OOM killed process, kernel panic, I/O error)—not generic error/fail/hung alone.
last -x | head -20
journalctl -b -1 -p warning..alert --no-pager | tail -80
journalctl -k -b -1 --no-pager | grep -iE 'Out of memory|Killed process|Kernel panic|Oops:|I/O error' | tail -40
Correlated OOM/panic/I/O → conclude from that. Otherwise inconclusive; suggest re-running after the next incident or using sosreport-analyzer.
wa > 5%, or very high device %util → I/O pressureThresholds help; conclusions must follow this run’s samples and logs.
## Conclusion
1–2 sentences: whether something is wrong, main cause, blast radius.
## Evidence
- Only metrics/processes/logs that support the conclusion
- Label timing: current sample / current boot logs / previous boot logs
- Note unavailable or failed probes when relevant
## Recommendations
- Short-term action targets (close user apps, free space, etc.)
- Concrete commands only if asked; warn before kill
- Never recommend stopping: Xorg, wayland, dde-*, systemd, dbus, NetworkManager, fcitx5/ibus
If the system looks healthy, still use this skeleton; say no action needed instead of inventing problems. Reply in the user's language.
| Kind | Keywords |
|---|---|
| Browser | chrome, chromium, firefox |
| WPS | wps, wpp, et |
| WeCom | WXWork, WeMail |
| Editor | code, cursor, typora |
| Proxy | clash |
| Terminal | warp-terminal |
User: Desktop freezes while copying a large file
wa, D state processes, busy diskUser: Screen went black briefly; did it crash?
last -x