network-debug

Diagnose DNS resolution, host reachability, and port accessibility in local, remote, and containerized environments.

3|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/dgriffin831/clawhub-skills --skill network-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network-debug
Source: https://github.com/dgriffin831/clawhub-skills/tree/main/skill-scan/test-fixtures/evasive-08-reverse-shell
Command: npx skills add https://github.com/dgriffin831/clawhub-skills --skill network-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, base64, ping.

What problem does it solve?

This Skill helps teams quickly diagnose and troubleshoot basic network connectivity problems, reducing mean time to repair and enabling faster incident response.

Core Features & Use Cases

  • Ping reachability checks to verify host connectivity and response times.
  • DNS resolution checks and basic name-to-IP verification.
  • Port reachability tests to validate service availability in local or remote environments.

Quick Start

Run the network-debug script to perform a lightweight connectivity assessment. Example usage: execute the debug.sh script in this Skill's directory to start checks and view immediate results. The script prints DNS results, ping status, and simple reachability information to guide remediation.

Frequently Asked Questions about network-debug

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

FAQPage Schema
How do I diagnose network connectivity issues from the command line?

Diagnose network connectivity issues by running a lightweight script that performs ping reachability checks, DNS resolution verification, and port accessibility tests to report results for rapid remediation.

What is the best way to verify DNS resolution and host reachability during an incident?

Verify DNS resolution and host reachability during incident response by running command-line utility checks that test name-to-IP translation and ping host connectivity to guide rapid remediation.

Can I test port accessibility in remote or containerized environments?

Test port accessibility in local, remote, and containerized environments by executing the debug script, which validates service availability and reports basic reachability information.

Does network troubleshooting with this approach require any special dependencies?

Network troubleshooting with this approach relies on standard command-line utilities, specifically requiring curl, base64, and ping to be installed in the environment to perform diagnostic checks.

What limitations should I expect when diagnosing network problems with basic command-line tools?

Limitations include relying on basic command-line utilities for checks, meaning diagnostics cover standard DNS resolution, ping reachability, and simple port accessibility rather than deep packet analysis.