debugging-network-issues
This skill applies falsification-first methodology to network and streaming incidents where the obvious cause is likely a red herring. Rather than stacking assumptions, it guides you through layered isolation—testing the same request across different paths to pinpoint exactly which hop (client, CDN, proxy, or backend) is responsible. Use it for connection resets, SSE stalls, fixed-time drops, certificate errors, or LAN mysteries where symptoms like "works sometimes" or "fails after N seconds" point to multiple possible layers.
Debugging Network Issues uses evidence-driven layered isolation to pinpoint network, streaming, and protocol bugs where symptoms mask the true cause.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
Debugging Network Issues uses evidence-driven layered isolation to pinpoint network, streaming, and protocol bugs where symptoms mask the true cause. This skill applies falsification-first methodology to network and streaming incidents where the obvious cause is likely a red herring. Rather than stacking assumptions, it guides you through layered isolation—testing the same request across different paths to pinpoint exactly which hop (client, CDN, proxy, or backend) is responsible. Use it for connection resets, SSE stalls, fixed-time drops, certificate errors, or LAN mysteries where symptoms like "works sometimes" or "fails after N seconds" point to multiple possible layers.
Use it when
- debugging-network-issues helps you separate these by testing the same request across different paths.
- debugging-network-issues guides you to apply layered isolation: test the same request from different clients (direct, VPN, proxy.
Verify before relying
Read SKILL.md below before installing (13 files). Open directory: indexed for reading, not audited.
Install
daymade/claude-code-skills/debugging-network-issues · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is debugging-network-issues and when should I use it?
debugging-network-issues applies falsification-first methodology to network and streaming incidents where the obvious cause is likely wrong. Use it when you face connection resets, SSE stalls, fixed-time drops, certificate errors, or LAN mysteries—especially when symptoms like "works sometimes" or "fails after N seconds" suggest multiple possible layers. Rather than stacking assumptions, it guides you through layered isolation to pinpoint exactly which hop (client, CDN, proxy, or backend) is responsible.
How do I distinguish upload timeout from backend processing timeout for large requests?
debugging-network-issues helps you separate these by testing the same request across different paths. Check reverse proxy access logs for bytes_read to see if the full body arrived; if it did but the response timed out, the backend is slow. If bytes_read is incomplete or the connection drops mid-upload, the upload itself is timing out. Test the same payload via direct connection, then through your CDN or proxy, to isolate which layer is enforcing the timeout.
What does connection reset ECONNRESET debugging involve?
debugging-network-issues guides you to apply layered isolation: test the same request from different clients (direct, VPN, proxy, different network), to different endpoints (direct backend, CDN, reverse proxy), and capture packets at each hop. If ECONNRESET happens only through one path, that hop is responsible. Check for idle timeouts, certificate mismatches, or proxy rules. Use packet capture to see whether the RST comes from your client, the proxy, CDN, or backend.
How can I resolve client-side proxy or VPN misrouting and CNAME rule conflicts?
debugging-network-issues recommends testing the same request with and without your proxy/VPN enabled, and inspecting DNS resolution to confirm the CNAME is resolving to the expected IP. Check your proxy's rule override settings and verify that SSL certificate verification isn't failing due to hostname mismatches. Use packet capture or a network analyzer to confirm which IP your traffic is actually reaching, then compare against your CNAME rule configuration.
How do I identify unknown LAN devices and diagnose subnet topology changes?
debugging-network-issues suggests scanning your LAN for mystery IPs and MAC addresses using ARP tables or network discovery tools. When topology changes cause connection drops at fixed intervals, check for DHCP lease expirations, gateway failovers, or TUN DNS hijacking. Correlate device appearance/disappearance with symptom timing. If getaddrinfo stalls, a resolver on your LAN may be misconfigured; test DNS directly against your gateway and upstream resolvers separately.
What is the core methodology behind debugging-network-issues?
debugging-network-issues uses falsification-first methodology: instead of assuming the obvious cause, you systematically test each layer in isolation. For each symptom, vary one factor at a time—client, path, endpoint, or timing—and record which combinations fail. This layered isolation experiment setup reveals which hop is actually responsible. By falsifying assumptions rather than confirming them, you avoid chasing red herrings and reach the true root cause faster.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Debugging Network Issues
Evidence-driven investigation methodology for incidents where the obvious cause is probably
(truncated - see the full file via the links below)
File tree — 13 files
debugging-network-issues/.security-scan-passed
debugging-network-issues/SKILL.md
debugging-network-issues/evals/evals.json
debugging-network-issues/references/case-cloudflare-524-upload.md
debugging-network-issues/references/case-proxy-tun-cname-override.md
debugging-network-issues/references/case-sse-rst-130s.md
debugging-network-issues/references/cognitive-traps.md
debugging-network-issues/references/counter-review-pattern.md
debugging-network-issues/references/instrumentation-patterns.md
debugging-network-issues/references/layered-isolation-experiment.md
debugging-network-issues/references/packet-capture-recipes.md
debugging-network-issues/scripts/layered-isolation-probe.sh
debugging-network-issues/scripts/mock-idle-upstream.py
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Debug network/streaming symptoms where obvious cause is probably wrong”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Tunnel Doctor isolates and resolves conflicts when Tailscale coexists with proxy/VPN tools like Shadowrocket, Clash, or Surge on macOS. It addresses route table corruption, environment variable misconfigurations, system proxy bypass issues, SSH double-tunneling, and VM/container proxy propagation problems—covering scenarios from browser 503 errors to Docker timeouts and WSL SSH access.
This skill guides you through pivoting and tunneling strategies to reach internal networks from a compromised host during authorized penetration tests. It covers SSH port forwarding, SOCKS proxies, and specialized tools like Chisel, Ligolo-ng, and sshuttle, with a decision tree to select the right approach based on available access and network constraints.
Master network tunneling and pivoting techniques to access internal systems from compromised hosts. This skill covers SSH port forwarding, reverse SOCKS proxies via Chisel, transparent TUN-based pivoting with Ligolo-ng, socat relays, DNS/ICMP/HTTP tunneling, ProxyChains configuration, Windows pivoting methods, and multi-layer chaining strategies.
This skill guides you through adding new subdomains to a Caddy-based network infrastructure. It gathers service details, validates inputs, updates your domains configuration, and applies changes across Caddy, Pi-hole DNS, and Cloudflare Access—then walks you through the final tunnel setup step.
Network Doctor guides you through systematic network diagnostics without risky guesswork. It establishes baseline measurements first, isolates root causes across ISP, Wi-Fi, DNS, MTU, proxy, and background processes, then proposes only reversible fixes with before-and-after verification.
This skill helps you troubleshoot organic traffic declines by systematically analyzing technical health, search ranking shifts, and content performance. It guides you through root-cause investigation to pinpoint whether issues stem from indexing problems, algorithm updates, competitor activity, or content quality gaps.
More skills windows-remote-desktop-connection-doctor (MIT) · systematic-debugging (MIT)