network-diagnosis

Name: network-diagnosis
Availability: InStock
Author: openEuler

Collect and analyze L1-L4 network snapshots to diagnose connectivity and packet loss.

3|2|Updated Apr 24, 2026

Search Tags:#troubleshooting #diagnosis #linux #connectivity #network #packet loss

Ready to run

npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill network-diagnosis-openeuler-mirror

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: network-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/network-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill network-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, iproute2, ethtool, arping, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of network troubleshooting by providing a structured, multi-layer diagnostic framework that identifies root causes for connectivity, latency, and packet loss issues without requiring manual intervention.

Core Features & Use Cases

Automated Snapshot Collection: Captures comprehensive system and network state data, including interface statistics, routing tables, and firewall rules, within a specific time window.
Multi-Layer Analysis: Systematically evaluates L1-L4 network layers, including ARP table health, IP conflict detection, and MTU path verification.
Use Case: When a server experiences intermittent packet loss, use this Skill to automatically collect diagnostic snapshots, correlate them with system logs, and receive a prioritized list of potential root causes and non-destructive remediation suggestions.

Quick Start

Use the network-diagnosis skill to analyze the connectivity issues on the eth0 interface for the last 30 minutes.

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 packet loss and latency spikes on a Linux server?▼

To diagnose intermittent packet loss and latency spikes on a Linux server, the network-diagnosis skill automatically collects system snapshots across L1-L4 layers, correlating interface statistics and kernel logs to identify root causes. It provides non-destructive, evidence-based remediation suggestions.

What is the best way to perform multi-layer network troubleshooting across L1 to L4 layers?▼

The best way to perform multi-layer network troubleshooting across L1 to L4 layers is to capture comprehensive system state data, including ARP table health, IP conflict detection, and MTU path verification, correlating these snapshots with routing tables and firewall rules for standardized reporting.

How do I automatically collect network diagnostic snapshots for connectivity failures?▼

You can automatically collect network diagnostic snapshots for connectivity failures by running the network-diagnosis skill, which captures interface statistics, routing tables, and firewall rules within a specific time window to provide an evidence-based root cause analysis.

Does Linux network fault diagnosis require manual intervention to identify root causes?▼

Linux network fault diagnosis does not require manual intervention to identify root causes when using this automated framework, which systematically evaluates interface statistics and kernel logs to generate a prioritized list of potential issues and non-destructive remediation suggestions.

Can I analyze eth0 connectivity issues for the last 30 minutes using this approach?▼

Yes, you can analyze eth0 connectivity issues for the last 30 minutes by invoking the skill to collect and correlate diagnostic snapshots within that specific time window, matching interface statistics against system logs to isolate the fault.

What dependencies are needed to perform automated network fault analysis in Linux environments?▼

To perform automated network fault analysis in Linux environments, the required dependencies include bash, iproute2, ethtool, and arping, which collectively enable systematic snapshot collection and multi-layer evaluation of interface and routing health.