Network Doctor
Use this skill to diagnose and improve local network performance without guessing or making unsafe system changes.
Scope
Handle:
- Slow internet speed, unstable latency, packet loss, DNS delay, MTU symptoms
- Wi-Fi signal/interference problems
- VPN, proxy, split tunnel, firewall, or filtering conflicts
- Background processes consuming bandwidth
- Stale network locations/profiles and mDNS oddities
- Windows TCP auto-tuning only when the user explicitly says Windows
Do not handle:
- General Mac slowness, browser slowness, local LLM speed, disk cleanup, app crashes
- Router admin changes unless the user explicitly asks and provides access
- Production network, office network, cloud infrastructure, or shared enterprise devices without explicit authorization
Required Workflow
- Read
references/safety.md.
- Classify the symptom before running commands:
- Bandwidth: low Mbps or unstable throughput
- Latency: high ping, jitter, video call lag, game lag
- DNS: websites pause before loading, IP ping is fine
- Wi-Fi/LAN: bad signal, far from router, roaming, interference
- VPN/proxy: only some sites slow, domestic/overseas split is wrong
- MTU/TCP: stalls, large downloads hang, VPN-specific breakage
- Background traffic: uploads/sync/downloads consume bandwidth
- Read
references/diagnostic-playbook.md.
- If the machine is macOS, read
references/commands-macos.md.
- Establish a before baseline before proposing changes.
- Make findings evidence-led. Use
[VERIFIABLE] for measured facts and [JUDGMENT 高/中/低] for interpretation.
- Separate actions into:
- Safe read-only checks already run
- Low-risk reversible actions
- Risky actions requiring explicit confirmation
- Actions to reject
- Change only one variable per pass.
- Run the same verification after each change.
- Use
references/report-template.md for the final response.
Command Policy
Allowed by default:
- Read-only diagnostics such as
networkQuality, ping, scutil --dns, ifconfig, route, netstat, ps
- Speed or latency tests that do not modify system state
Require explicit user confirmation:
- Killing or throttling processes
- Flushing DNS cache
- Restarting mDNSResponder
- Changing DNS, MTU, proxy, VPN, firewall, TCP parameters, network service order, or network location
- Deleting stale profiles or locations
- Router or modem changes
- Any command requiring
sudo
Reject unless the user gives a narrow, reversible reason:
- Bulk deletion of network settings
- Disabling security tools blindly
- Random "optimization" commands from the internet
- Multiple simultaneous changes that make before/after verification meaningless
Output Standard
Always give the user:
- What was tested
- What changed, if anything
- What the evidence says
- What remains unknown
- The exact before/after metrics
- Rollback steps for every modification
When the user wants a prompt to reuse, provide a compact /goal style prompt that includes constraints: read-only first, no unsafe changes, one change per pass, rollback, before/after test.
1---
2name: network-doctor
3description: "USE THIS SKILL whenever user says 网络慢、网速慢、网速优化、网络延迟高、Wi-Fi 慢、DNS 慢、MTU 问题、packet loss、VPN/代理影响网速、mDNS 异常、speedtest-cli, or asks Codex to make the internet/network faster. Diagnose network performance with read-only baselines first, separate ISP/Wi-Fi/DNS/MTU/proxy/background-process causes, then propose reversible fixes with before/after verification."
4metadata:
5 source: https://skillmd.com/skills/lltx/network-doctor
6---
7
8# Network Doctor
9
10Use this skill to diagnose and improve local network performance without guessing or making unsafe system changes.
11
12## Scope
13
14Handle:
15- Slow internet speed, unstable latency, packet loss, DNS delay, MTU symptoms
16- Wi-Fi signal/interference problems
17- VPN, proxy, split tunnel, firewall, or filtering conflicts
18- Background processes consuming bandwidth
19- Stale network locations/profiles and mDNS oddities
20- Windows TCP auto-tuning only when the user explicitly says Windows
21
22Do not handle:
23- General Mac slowness, browser slowness, local LLM speed, disk cleanup, app crashes
24- Router admin changes unless the user explicitly asks and provides access
25- Production network, office network, cloud infrastructure, or shared enterprise devices without explicit authorization
26
27## Required Workflow
28
291. Read `references/safety.md`.
302. Classify the symptom before running commands:
31 - Bandwidth: low Mbps or unstable throughput
32 - Latency: high ping, jitter, video call lag, game lag
33 - DNS: websites pause before loading, IP ping is fine
34 - Wi-Fi/LAN: bad signal, far from router, roaming, interference
35 - VPN/proxy: only some sites slow, domestic/overseas split is wrong
36 - MTU/TCP: stalls, large downloads hang, VPN-specific breakage
37 - Background traffic: uploads/sync/downloads consume bandwidth
383. Read `references/diagnostic-playbook.md`.
394. If the machine is macOS, read `references/commands-macos.md`.
405. Establish a before baseline before proposing changes.
416. Make findings evidence-led. Use `[VERIFIABLE]` for measured facts and `[JUDGMENT 高/中/低]` for interpretation.
427. Separate actions into:
43 - Safe read-only checks already run
44 - Low-risk reversible actions
45 - Risky actions requiring explicit confirmation
46 - Actions to reject
478. Change only one variable per pass.
489. Run the same verification after each change.
4910. Use `references/report-template.md` for the final response.
50
51## Command Policy
52
53Allowed by default:
54- Read-only diagnostics such as `networkQuality`, `ping`, `scutil --dns`, `ifconfig`, `route`, `netstat`, `ps`
55- Speed or latency tests that do not modify system state
56
57Require explicit user confirmation:
58- Killing or throttling processes
59- Flushing DNS cache
60- Restarting mDNSResponder
61- Changing DNS, MTU, proxy, VPN, firewall, TCP parameters, network service order, or network location
62- Deleting stale profiles or locations
63- Router or modem changes
64- Any command requiring `sudo`
65
66Reject unless the user gives a narrow, reversible reason:
67- Bulk deletion of network settings
68- Disabling security tools blindly
69- Random "optimization" commands from the internet
70- Multiple simultaneous changes that make before/after verification meaningless
71
72## Output Standard
73
74Always give the user:
75- What was tested
76- What changed, if anything
77- What the evidence says
78- What remains unknown
79- The exact before/after metrics
80- Rollback steps for every modification
81
82When the user wants a prompt to reuse, provide a compact `/goal` style prompt that includes constraints: read-only first, no unsafe changes, one change per pass, rollback, before/after test.