skills.rest
nimadorostkar
nimadorostkarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

network-troubleshooting

Diagnose network connectivity failures across DNS, TCP, TLS, and HTTP layers.

25|3|Updated Jul 14, 2026
Search Tags:#debugging#troubleshooting#networking#connectivity#dns#tls
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill network-troubleshooting-nimadorostkar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: network-troubleshooting
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/devops/network-troubleshooting
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill network-troubleshooting-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork in network debugging by providing a structured, layer-by-layer isolation methodology to identify whether a failure stems from DNS, TCP, TLS, or application-level issues.

Core Features & Use Cases

  • Layer-by-Layer Isolation: Systematically verify DNS resolution, socket connectivity, TLS handshakes, and HTTP requests.
  • Diagnostic Tooling: Provides expert guidance on using standard utilities like dig, nc, openssl, and curl to pinpoint the exact failing component.
  • Use Case: When a service in a Kubernetes cluster reports intermittent connection timeouts, use this skill to determine if the issue is caused by DNS search-path latency, ephemeral port exhaustion, or firewall packet drops.

Quick Start

Use the network-troubleshooting skill to diagnose the connection timeout error occurring between the frontend service and the backend API.

Frequently Asked Questions about network-troubleshooting

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

FAQPage Schema
How do I troubleshoot network connectivity failures in a Kubernetes cluster?▼

Troubleshoot Kubernetes network connectivity failures by systematically isolating issues across DNS resolution, TCP socket connectivity, TLS handshakes, and HTTP requests to pinpoint the exact failing component causing service timeouts.

What is the best way to debug intermittent service timeouts in cloud infrastructure?▼

Debug intermittent cloud infrastructure service timeouts using a layer-by-layer isolation methodology to determine if failures stem from DNS search-path latency, ephemeral port exhaustion, or firewall packet drops.

Can I use standard Linux networking utilities to verify TLS handshake success?▼

Yes, you can verify TLS handshake success and protocol-specific connectivity using standard Linux networking utilities like openssl and curl to isolate application-level issues from transport-layer failures.

Why does my service connection timeout occur between frontend and backend API layers?▼

Service connection timeouts between frontend and backend APIs occur due to failures across DNS, TCP, TLS, or HTTP layers, requiring systematic isolation to determine if the root cause is network path reachability or protocol handshake failure.

When should I not use layer-by-layer isolation for network debugging?▼

Layer-by-layer isolation for network debugging is not ideal when standard Linux networking utilities are unavailable or when failures are confirmed to be purely application-logic errors rather than DNS, TCP, TLS, or HTTP connectivity issues.

Related Skills

Explore More Software Engineering Skills→
albertdobmeyeralbertdobmeyer
2

dns-networking

Diagnose DNS resolution and network connectivity failures using command-line tools.

Community
Intermediate
kimasplundkimasplund

qavr-status

Display QAVR memory system status and configuration in a diagnostic report.

Community
Basic
ChrstprJohnChrstprJohn

service-mesh-expert

Automate service mesh design and deployment across Istio and Linkerd on Kubernetes.

Community
Advanced
ErixWongErixWong
17

net-operations

Perform DNS lookups, SSL certificate analysis, and HTTP header checks.

Community
Intermediate