Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Connectivity Troubleshooter

    1

    Diagnose network connectivity failures across DNS, TCP, TLS, and HTTP layers with automated CLI probing.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Connectivity Troubleshooter

    Connectivity Troubleshooter

    Example session with this skill installed

    Diagnose connectivity for https://api.internal.dev, db-prod.cluster:5432, and smtp.provider.com:587. Check against internal DNS 10.0.0.5.

    • Read your context and instructions
    • Compiled the connectivity troubleshooter

    I have initiated a layer-by-layer connectivity scan for the three requested targets. The diagnostic checked DNS resolution (using system and 10.0.0.5), TCP handshakes, TLS integrity, and HTTP response headers.

    Connectivity Diagnostic Results

    TargetLayerStatusLatencyDetails
    https://api.internal.devHTTPFAIL45msDNS/TCP/TLS OK. HTTP 403 Forbidden. Check API key or IP whitelist.
    db-prod.cluster:5432TCPFAIL2001msDNS OK. TCP Connection Timeout. Likely firewall/Security Group blocking port 5432.
    smtp.provider.com:587TLSWARN112msTCP OK. TLS Handshake OK, but Certificate expires in 3 days (2025-05-20).

    Detailed Log Output

    [api.internal.dev]
    - DNS (10.0.0.5): 10.0.5.22 [OK]
    - TCP 443: Connected in 12ms [OK]
    - TLS: Subject: CN=api.internal.dev, Issuer: Internal CA [OK]
    - HTTP: GET / -> 403 Forbidden [ERROR]
    
    [db-prod.cluster:5432]
    - DNS (10.0.0.5): 10.0.8.105 [OK]
    - TCP 5432: Connection timed out after 2.0s [ERROR]
    - Analysis: Port is filtered or host is down.
    
    [smtp.provider.com:587]
    - DNS (10.0.0.5): 172.64.155.1 [OK]
    - TCP 587: Connected in 42ms [OK]
    - TLS: STARTTLS Handshake successful. Expiring soon. [WARN]
    

    Next steps

    1. Review the IAM/Auth policy for api.internal.dev to resolve the 403 Forbidden error.
    2. Verify the ingress rules for port 5432 on the db-prod.cluster security group.
    3. Renew the TLS certificate for the SMTP relay to avoid service interruption next week.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Connectivity issues are often met with guesswork and trial-and-error. This skill replaces vague hunches with a systematic, layer-by-layer diagnosis of hostnames, ports, and URLs. It pinpoints exactly where the connection drops, whether it is a DNS resolution failure, a firewall timeout, an expired TLS certificate, or an application-level error.

    What it does

    • Multi-layer diagnostics tests DNS resolution, TCP connectivity, TLS handshakes, and HTTP response status in a single pass.
    • TLS validation extracts certificate expiry, issuer, and SANs while flagging hostname mismatches or self-signed certs.
    • Intermittent failure detection runs repeated checks over a set interval to capture transient networking drops.
    • Split-horizon DNS testing compares local system resolution against specific upstream DNS servers using dig.
    • Bulk processing handles multiple targets simultaneously from command line arguments or a text file.

    How it works

    1. Targeting involves providing a list of URLs, hostnames, or host:port pairs via the CLI or a file.
    2. Analysis triggers the automated sequence from DNS lookup through to the HTTP application layer.
    3. Isolation identifies the specific failure point, such as a closed port, routing timeout, or protocol error.
    4. Reporting generates a structured summary or CSV export detailing the latency and status of every layer.

    Frameworks & tools

    The skill utilizes a Python-based execution script (conncheck.py) and standard networking utilities like dig. It relies on the local environment's network stack to reflect accurate routing and firewall conditions.

    Why this beats prompting it yourself

    Generic AI prompts often suggest basic steps like "check your cable." This skill executes precise technical probes that return raw data on TCP handshake timings and TLS handshake internals, providing the empirical evidence needed to open a firewall ticket or fix a DNS record.

    Use cases

    • Service health sweeps to verify all backend dependencies and databases are reachable after a deployment.
    • Firewall auditing to confirm if specific ports are open between VPCs or across a VPN.
    • Certificate monitoring to proactively identify endpoints with expiring or misconfigured TLS certs.

    Known limitations

    Requires Python 3 and local execution to accurately reflect network path issues. Results are limited by the permissions and routing tables of the host machine.

    Requires Python 3 and local execution. Accuracy depends on the host machine's specific network environment, routes, and firewall rules.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill systematically tests each layer of a connection—DNS, TCP, TLS, and HTTP—to pinpoint exactly where a failure occurs, eliminating the guesswork of manual pings or generic troubleshooting steps.

    The skill requires a Python 3 environment and standard networking tools like `dig`. It is designed to work with AI agents that have CLI execution capabilities, allowing them to run the `conncheck.py` script locally.

    Yes, the skill includes a bulk processing feature that can ingest multiple targets from a text file or command-line arguments, making it ideal for large-scale service health sweeps.

    You will receive the core Python execution script, comprehensive documentation on CLI arguments, and a set of integration instructions to help your AI agent interpret the diagnostic reports.

    Because the skill executes from your local machine or server, it reflects the actual routing, firewall rules, and VPC configurations of your environment for 100% accurate results.

    New in Testing & Debugging