diagnose-system-lag

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"]

System lag diagnosis

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.

Rules

1. Read-only: do not change config, kill processes, drop caches, tune sysctl, or unload modules.
2. Symptom-first: decide what to probe from the user's report; do not run a fixed full command list every time.
3. Stop when enough: stop once the symptom is explained and key objects (process / mount / device) are named.
4. Follow-ups fill gaps only: the next probe answers “what is still missing”, not “scan every focus again”.
5. Advice needs confirmation: prefer action targets; give concrete kill/restart commands only if asked, and remind the user to save work.
6. Isolated sessions: do not run report-writing scripts under this skill (for example scripts/diagnose.sh).
7. Honest probes: if a tool is missing or a probe fails, state that in Evidence—do not treat it as “no problem found”.

Workflow

Understand symptom → quick check (only if vague) → focused probes → answer
                         ↑ stop when evidence is enough ↑

1. Understand the symptom

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.