X-diagnosis-network-analysis

Diagnose Linux network failures in real time using X-diagnosis probing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Linux network issues often go undiagnosed due to reliance on offline logs; this skill enables real-time, in-host network fault diagnosis with the X-diagnosis toolkit to quickly identify root causes.

Core Features & Use Cases

  • Real-time online fault detection across NICs, routes, and kernel counters using dedicated diagnosis tools.
  • Stepwise workflow (baseline collection, scene classification, deep probing, evidence cross-check, and structured reporting) to ensure repeatable, auditable results.
  • Comprehensive reference materials and scripts to perform deterministic checks and generate actionable findings for Linux network problems (e.g., ARP storms, TCP resets, packet drops).

Quick Start

Run the baseline collection script and follow the Step 1–Step 4 workflow to diagnose the current network issue.

Frequently Asked Questions about X-diagnosis-network-analysis

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

FAQPage Schema
How do I diagnose Linux network packet loss in real time instead of relying on offline logs?

You can diagnose Linux network packet loss in real time by running baseline collection and deep probing scripts to identify root causes directly on the server. This avoids offline log analysis limitations by inspecting live kernel counters and network interfaces.

What's the best way to troubleshoot ARP storms and TCP connection resets on a Linux server?

Troubleshooting ARP storms and TCP resets requires online probing rather than offline log analysis. A stepwise workflow of baseline collection, scene classification, timed analysis, and cross-check validation identifies the root cause of these network issues.

Does real-time network diagnosis work for latency spikes and link drops without taking the server offline?

Real-time network diagnosis works for latency spikes and link drops without server downtime by performing in-host online probing. It inspects live NICs, routes, and kernel counters to detect ongoing faults directly on the Linux server.

How do I start a structured network fault diagnosis to find the root cause of TCP connection issues?

Start structured network fault diagnosis by running the Step 0 baseline collection script to gather current state. Follow the Step 1 through Step 4 workflow to classify scenes, trace with tools, cross-check evidence, and generate a structured report.

Can I use xd_ntrace for timed analysis to capture intermittent network faults?

You can use xd_ntrace for timed analysis to capture intermittent Linux network faults. It performs online probing during specific time windows to detect transient issues like latency spikes and packet drops that offline logs miss.

What are the limitations of online probing for Linux network diagnosis compared to offline log analysis?

Online probing limitations include requiring active server access and focusing on live state rather than historical trends. It diagnoses current Linux network issues like packet drops and ARP storms but cannot analyze past offline logs for retrospective auditing.