network_diagnosis

Diagnose network connectivity issues across DNS, ping, port, and HTTP checks.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ougi777/Mutil-AIops-Agent --skill network-diagnosis-ougi777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network_diagnosis
Source: https://github.com/ougi777/Mutil-AIops-Agent/tree/main/app/skills/definitions/network_diagnosis
Command: npx skills add https://github.com/ougi777/Mutil-AIops-Agent --skill network-diagnosis-ougi777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through end-to-end network diagnosis to determine why a website is unreachable, an API times out, DNS resolves incorrectly, or a port appears closed.

Core Features & Use Cases

  • DNS and domain reachability checks: validate DNS resolution and domain accessibility.
  • Layered connectivity tests: perform ping, port checks, and HTTP requests to isolate where failures occur.
  • Use Case: When a site fails to load, run DNS lookup, ping the host, check the port, and send an HTTP request to identify the failure stage and remediation steps.

Quick Start

Run a guided diagnostic sequence against the target URL or host to determine the failing component and suggest fixes.

Frequently Asked Questions about network_diagnosis

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

FAQPage Schema
How do I diagnose why a website is unreachable or an API times out?

To diagnose network connectivity issues, run a sequential guided diagnostic sequence that performs DNS lookup, ping, port checks, and HTTP requests to isolate the failure stage and provide remediation steps.

What steps are needed to troubleshoot DNS resolution and port reachability for a remote host?

Troubleshooting DNS and port reachability requires running layered connectivity tests that validate domain resolution, ping the host, check target ports, and send HTTP requests to identify where the connection drops.

Can I check if a specific port is closed or open using an end-to-end network diagnosis?

Yes, end-to-end network diagnosis includes port reachability checks as part of its layered connectivity tests, allowing you to determine if a specific port appears closed and identify the root cause.

Why does my HTTP request fail even though DNS resolves correctly?

An HTTP request can fail despite correct DNS resolution if port reachability is blocked or the server fails to respond, which a sequential diagnostic test isolates by checking ping, ports, and HTTP status sequentially.

What is the best way to identify the root cause of incorrect DNS resolution for a domain?

The best way to identify root causes of incorrect DNS resolution is running a structured diagnostic sequence that validates domain accessibility and cross-references DNS lookup results with ping and HTTP checks.

When should I not use a general network connectivity diagnosis tool?

General network connectivity diagnosis is not suitable for deep packet-level traffic analysis or continuous real-time monitoring, as it focuses on sequential endpoint testing and structured inference for isolated failures.