it-network-diagnostics

Diagnoses enterprise network connectivity failures across DNS, VPN, TLS, and transport layers.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-network-diagnostics-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-network-diagnostics
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-network-diagnostics
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-network-diagnostics-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Network outages and connectivity complaints are hard to triage because failures can occur at any layer—link, DNS, routing, TLS, or application. This Skill provides a layered diagnostic workflow that isolates the failing layer with evidence instead of guesswork, avoiding risky broad firewall or routing changes. ## Core Features & Use Cases - Layered Diagnosis: Systematically tests link/IP configuration, DNS resolution, transport reachability, TLS certificate validity, and application response to pinpoint the failing layer. - Symptom-to-Evidence Matrix: Maps common symptoms (no IP, DNS failure, VPN failure, certificate warnings, intermittent slowness, single-site outages) to the exact evidence to collect. - Safe Change Governance: Enforces rules against any/any firewall rules, TLS weakening, or unapproved production changes, requiring scope, rollback, and verification for every modification. - Use Case: A user reports "no internet" on VPN. The Skill guides checking client IP configuration, split-horizon DNS, tunnel routes, and proxy settings, then correlates VPN and firewall logs in the same time window to identify the failing layer and propose a minimal, reversible fix. ## Quick Start Diagnose why users on the office Wi-Fi cannot reach the internal application at app.contoso.com and identify the failing network layer.

Frequently Asked Questions about it-network-diagnostics

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

FAQPage Schema
How do I troubleshoot a VPN that connects but applications still fail?▼

Check VPN routes, DNS resolution, proxy settings, authorization policies, and overlapping subnets after the tunnel establishes. A successful VPN connection only proves tunnel negotiation, not that traffic reaches the application path.

How to diagnose DNS resolution failures on a network?▼

Test the query against the configured resolver and record the response code, answer, TTL, and cache state. Compare split-horizon behavior and authoritative records, and check whether the failure is device-specific or affects an entire segment.

Why does ping fail when the application still works?▼

Ping failure does not prove service failure because ICMP is often blocked by firewall policy while application ports remain open. Always test the actual protocol and port the application uses instead of relying on ping.

Can I temporarily disable TLS inspection to fix certificate warnings?▼

No. Ignoring certificate warnings or weakening TLS is rejected as a workaround. Repair the actual cause such as hostname mismatch, incomplete chain, expired certificate, trust store, server binding, or device clock.

What evidence should I collect for intermittent network slowness?▼

Collect latency, packet loss, jitter, link utilization, retransmission rates, Wi-Fi signal strength, and the time pattern of occurrences. Preserve the telemetry window so recurrence can be monitored against defined criteria.

What are the limitations of automated network troubleshooting?▼

A successful local test does not prove all users or paths are restored, and diagnostics require authorized access to logs and devices. Production routing, DNS, firewall, or certificate changes require explicit scope, approval, and rollback plans.