菜单
Use when diagnosing DNS, TCP connectivity, ping reachability, network interfaces, service ports, or network-related SysGuard incidents.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating structured incident alerts from SysGuard findings, health reports, log analysis, remediation failures, or operational events.
Use when checking database connectivity, running read-only diagnostic SQL, validating DSNs, or collecting small database health evidence through SysGuard.
Use when reading, statting, listing, or tailing local files for SysGuard diagnostics without modifying filesystem contents.
Use when checking host health, service health, CPU, memory, disk, network status, or determining whether SysGuard should treat a system as unhealthy.
Use when analyzing operational logs, filtering errors or warnings, summarizing incidents from log files, or finding relevant lines in SysGuard-managed logs.
Use when collecting structured CPU, memory, disk, network, service, or health-score metrics from SysGuard for dashboards or reports.
| name | network-diagnosis |
| description | Use when diagnosing DNS, TCP connectivity, ping reachability, network interfaces, service ports, or network-related SysGuard incidents. |
Use this skill to isolate whether an incident is caused by name resolution, interface state, TCP connectivity, or host reachability.
The Go implementation is registered by RegisterCoreSkills and invoked as "network-diagnosis":
registry.Execute(ctx, "network-diagnosis", &skills.SkillInput{Params: map[string]interface{}{
"operation": "tcp",
"host": "example.com",
"port": 443,
"timeout": "5s",
}})
Supported operations are interfaces, dns, tcp, and ping.
interfaces for local network suspicion.dns when hostnames fail or resolve unexpectedly.tcp for service-port reachability.ping only as a coarse reachability signal; ICMP can be blocked.Do not run scanning or broad port sweeps from this skill. Diagnose only the host and port relevant to the incident.