Network Troubleshooting

This skill provides a concise, safety-first decision guide for diagnosing developer network failures. Diagnostics must stay read-only and target-scoped — this is not an automated remediation toolkit.

Safety Boundaries

These boundaries apply to every step of the workflow below and must never be relaxed, even if asked:

• Prefer read-only diagnostics and trusted project-provided diagnostic scripts.
• Use the failing host, URL, registry, or service as the default probe target — do not probe unrelated hosts.
• Ask before probing unrelated external services.
• Never print proxy URLs, credentials, tokens, auth headers, package index URLs, registry hostnames from config, or raw config values in shared output.
• Internal hosts and URLs may be collected for target-scoped local diagnostics, but replace them with placeholders before sharing logs or reports unless the user explicitly approves including them.
• Never dump local configuration from npm, pnpm, yarn, pip, Git, Docker, shell, OS proxy, VPN, or certificate stores.
• Never disable, bypass, or skip TLS or certificate verification (no -k/--insecure, no NODE_TLS_REJECT_UNAUTHORIZED=0, no verify=False), even temporarily "just to test."
• Never change OS networking, DNS, proxy, package manager, Git, Docker, shell, VPN, or trust-store settings without explicit user approval for the exact action being taken.

Workflow