network_diagnosis

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

115|13|Updated May 5, 2026
One-click install
npx skills add https://github.com/Kkkirito-123/mutil-rag-agent --skill network-diagnosis-kkkirito-123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network_diagnosis
Source: https://github.com/Kkkirito-123/mutil-rag-agent/tree/main/app/skills/definitions/network_diagnosis
Command: npx skills add https://github.com/Kkkirito-123/mutil-rag-agent --skill network-diagnosis-kkkirito-123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose network connectivity problems across websites and services, by tracing DNS, host reachability, port status, and HTTP responsiveness to identify root causes and guide remediation.

Core Features & Use Cases

  • DNS resolution: verify domain names resolve to IPs and detect DNS misconfigurations.
  • Reachability checks: confirm host accessibility via ping and route assessment.
  • Port & HTTP checks: verify port openness and HTTP response details to distinguish between network and application issues.
  • Typical use case: When a website is not loading, API calls timeout, or DNS looks up incorrectly, run this playbook to surface the underlying network problem and suggested fixes.

Quick Start

Run the network_diagnosis diagnostic on the target URL or host to obtain a structured report of DNS, ping, port, and HTTP results.

Frequently Asked Questions about network_diagnosis

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

FAQPage Schema
How do I diagnose network connectivity issues when a website or API is not loading?

Diagnosing network connectivity involves tracing DNS resolution, ICMP ping host reachability, port status, and HTTP response details to identify root causes and produce structured remediation guidance for websites or APIs not loading.

What is the best way to troubleshoot DNS resolution errors for a domain?

Troubleshooting DNS resolution errors involves performing DNS lookups to verify domain names resolve to correct IPs and detect misconfigurations, which helps isolate whether the issue lies in DNS or network reachability.

How can I check if a network port is open or blocked for a specific host?

Checking if a network port is open involves running port reachability checks against the target host to verify port openness, helping you distinguish between network-level blocks and application-level failures.

Why does my HTTP request timeout and how can I find the underlying network problem?

HTTP request timeouts often stem from DNS failures, unreachable hosts, or blocked ports; running a structured network diagnosis that performs DNS lookups, pings, port checks, and HTTP requests surfaces the exact underlying network problem.

Can I use automated network diagnosis to distinguish between network and application issues?

Yes, automated network diagnosis distinguishes network from application issues by sequentially verifying DNS resolution, host reachability via ping, port openness, and HTTP response details to pinpoint the exact failure layer.

What should I do when network diagnosis shows DNS is correct but the host is unreachable?

When DNS is correct but the host is unreachable, the network diagnosis report guides remediation by assessing route reachability and port status, suggesting fixes for network blocks, firewall rules, or host downtime.