Agent Skills › ryantsai/KKTerm › network-connectivity-troubleshooter

network-connectivity-troubleshooter

GitHub

用于诊断 KKTerm 中网络连通性故障，涵盖主机不可达、路由、网关、VPN、代理、丢包及延迟等问题。通过分层检查（DNS、接口、路由等）和多视角对比，提供只读命令建议以定位问题根源。

assistant-skills/network-connectivity-troubleshooter/SKILL.md ryantsai/KKTerm

Trigger Scenarios

用户询问为何特定主机或服务无法连接报告网络连接不稳定、高延迟或间歇性中断需要排查 DNS 解析失败或路由配置错误

Install

npx skills add ryantsai/KKTerm --skill network-connectivity-troubleshooter -g -y

More Options

Non-standard path

npx skills add https://github.com/ryantsai/KKTerm/tree/main/assistant-skills/network-connectivity-troubleshooter -g -y

Use without installing

npx skills use ryantsai/KKTerm@network-connectivity-troubleshooter

指定 Agent (Claude Code)

npx skills add ryantsai/KKTerm --skill network-connectivity-troubleshooter -a claude-code -g -y

安装 repo 全部 skill

npx skills add ryantsai/KKTerm --all -g -y

预览 repo 内 skill

npx skills add ryantsai/KKTerm --list

SKILL.md

Frontmatter

{
    "name": "network-connectivity-troubleshooter",
    "description": "Diagnose general network connectivity failures in KKTerm, including unreachable hosts, routing, gateway, VPN, proxy, packet loss, latency, MTU, and local-vs-remote reachability checks."
}

Network Connectivity Troubleshooter

Use this skill when the user asks why a host, service, Connection, URL, or remote network path is unreachable or unreliable.

Workflow

Identify the vantage point: local Windows shell, WSL, SSH Session, remote host, VPN, or another network segment.
Clarify the target as narrowly as possible: host/IP, port/protocol if known, and whether the failure is total, intermittent, slow, or one app only.
Separate layers before suggesting fixes: name resolution, local interface, default gateway, route, VPN/proxy, firewall, remote listener, and application protocol.
Prefer read-only checks first: interface state, IP address, route table, DNS answer, ping when allowed, TCP connect test, and traceroute/path trace.
Compare at least two vantage points when possible, such as local KKTerm terminal vs SSH Session from a nearby host.
Treat ICMP results carefully. A failed ping does not prove TCP is blocked, and a successful ping does not prove the service is healthy.
For intermittent loss or latency, ask for timing, affected destinations, wired vs wireless/VPN state, and recent network changes before recommending resets.
For MTU symptoms, look for large transfers hanging, VPN-only failures, TLS stalls, or SSH/SFTP freezes after login.
Avoid broad reset commands until targeted evidence points to local network stack corruption.

Command Guidance

Windows reachability: Test-NetConnection <host> -Port <port> for TCP, Resolve-DnsName <host> for DNS, and tracert <host> for path checks.
PowerShell interface/routing: Get-NetIPConfiguration, Get-NetRoute, Get-DnsClientServerAddress.
POSIX/SSH vantage point: ip addr, ip route, getent hosts <host>, nc -vz <host> <port>, tracepath <host> or traceroute <host> when installed.
Keep commands read-only unless the user explicitly asks to change adapter, VPN, proxy, or route configuration.

KKTerm Boundaries

Stored targets are Connections; live failures happen in Sessions.
Quick Connect failures may come from draft fields that are not saved yet.
URL Connections use embedded WebView2 and may be affected by OS proxy, TLS, or corporate inspection.
SSH, SFTP, RDP, VNC, URL, and local terminal checks can all provide different network vantage points.