network-diagnosis

Diagnose Linux network faults by aggregating multi-source telemetry into root-cause reports.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/linfordWu/owls --skill network-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network-diagnosis
Source: https://github.com/linfordWu/owls/tree/main/skills/network-diagnosis
Command: npx skills add https://github.com/linfordWu/owls --skill network-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides systematic network fault diagnosis by collecting and correlating multi-source telemetry (interfaces, routes, ARP, firewall, conntrack, MTU) to identify root causes.

Core Features & Use Cases

  • Multi-source snapshot collection across interfaces, routes, ARP, DNS, and logs for accurate diagnostics.
  • Phase-driven workflow with strict sequencing and cross-source validation to prevent premature conclusions.
  • Generates structured root-cause reports with actionable remediation guidance for both single-interface issues and whole-host outages.
  • Real-world use cases include diagnosing a specified interface going down, diagnosing intermittent connectivity across the server, and validating routing or firewall misconfigurations.

Quick Start

Run the diagnostic workflow to collect a complete network snapshot and begin analysis.

Frequently Asked Questions about network-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose intermittent network connectivity issues on a Linux server?

To diagnose intermittent network connectivity on a Linux server, this Skill aggregates multi-source telemetry including interfaces, routes, ARP, and conntrack to identify root causes. It applies strict time-window collection and cross-source validation to prevent premature conclusions.

What is the best way to troubleshoot conntrack saturation and firewall behavior on Linux?

Troubleshooting conntrack saturation and firewall behavior requires correlating multi-source telemetry. This Skill collects snapshots across interfaces, routes, and firewall states, applying cross-source validation to deliver structured root-cause reports with actionable remediation guidance.

How do I identify the root cause of an ARP issue or IP conflict on a specified interface?

Identifying root causes of ARP issues or IP conflicts involves correlating interface, route, and ARP data. This Skill collects multi-source network snapshots across specified interfaces and validates them cross-source to generate structured reports with actionable safety controls.

Can I use this network diagnosis workflow for full-host outages across multiple interfaces?

Yes, you can use this network diagnosis workflow for full-host outages. It handles both specified single-interface issues and whole-host scenarios by enforcing phase-driven sequencing and aggregating telemetry across interfaces, routes, DNS, and logs.

How does cross-source validation prevent premature conclusions during network fault diagnosis?

Cross-source validation prevents premature conclusions during network fault diagnosis by enforcing strict phase-driven sequencing. It correlates multi-source telemetry from interfaces, routes, ARP, firewall, conntrack, and MTU before delivering structured root-cause reports.

What are the limitations of diagnosing routing problems without strict time-window collection?

Diagnosing routing problems without strict time-window collection risks missing intermittent faults. This Skill enforces time-window collection and cross-source validation to ensure accurate root-cause identification across interfaces, routes, and firewall behavior.