Ping

v1.0.0

Monitor network connectivity and diagnose latency issues using ping and traceroute. Use when troubleshooting network problems or checking host availability.

0· 193·1 current·1 all-time
bybytesagain4@xueyetianya
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the implementation: the script runs ping/traceroute/tracepath, provides check/trace/sweep/monitor/report commands and stores results locally. Required tools (ping, traceroute/tracepath, python3) are appropriate for the stated purpose.
Instruction Scope
The runtime instructions and script stay within the diagnostic scope but perform a subnet sweep (PING_SUBNET) which actively probes many hosts — this is coherent with a network-scan feature but can be intrusive on networks you don't own/operate. The tool only reads/writes ~/.ping and uses environment variables documented in SKILL.md; it does not access other system paths or external endpoints.
Install Mechanism
No install spec; code is included as a shell script. Nothing is downloaded from the network or written to system-wide locations. This low-risk packaging is consistent with a simple utility.
Credentials
No secrets or unrelated environment variables are required. The declared environment variables (PING_*) match the script's behavior and purpose.
Persistence & Privilege
The skill creates and writes persistent files under ~/.ping (data.jsonl and config.json) for history—this is expected behavior but users should be aware of local storage of probe history and config changes.
Assessment
This skill appears to do what it says: run pings/traceroutes, sweep subnets, monitor and save results locally. Before installing, review the included script (scripts/script.sh) yourself and be comfortable with it creating ~/.ping and appending probe history. Be careful using the sweep feature on networks you don't own (it actively probes many hosts and may violate policy). Ensure you have the required binaries (ping, traceroute/tracepath, python3) and be aware that ping options may vary by OS (macOS vs Linux). If you need no persistent history, run commands manually or delete ~/.ping afterward.

Like a lobster shell, security has layers — review code before you run it.

latestvk979xwbnyeb1mdyzq2z62pcres836skb
193downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Ping — Network Connectivity Tool

A thorough network connectivity diagnostic tool that checks host availability, traces routes, sweeps subnets, monitors uptime, and analyzes latency patterns. All results are stored locally in JSONL format for historical analysis and reporting.

Prerequisites

  • ping command (pre-installed on most systems)
  • traceroute or tracepath (for route tracing)
  • python3 (for data processing and reporting)
  • bash 4.0+

Data Storage

All ping results and configuration are stored in ~/.ping/:

  • ~/.ping/data.jsonl — historical ping results (JSONL format)
  • ~/.ping/config.json — user configuration (default count, timeout, etc.)

Commands

check

Check connectivity to a target host. Sends ICMP echo requests and records results.

PING_TARGET="8.8.8.8" PING_COUNT="4" bash scripts/script.sh check

trace

Trace the network route to a target host, showing each hop and latency.

PING_TARGET="google.com" bash scripts/script.sh trace

sweep

Sweep a subnet to discover responsive hosts. Scans a CIDR range.

PING_SUBNET="192.168.1.0/24" bash scripts/script.sh sweep

monitor

Continuously monitor a host and log results. Runs a configurable number of pings over time.

PING_TARGET="8.8.8.8" PING_INTERVAL="5" PING_DURATION="60" bash scripts/script.sh monitor

report

Generate a summary report from stored ping history for a specific target or all targets.

PING_TARGET="8.8.8.8" bash scripts/script.sh report

latency

Analyze latency statistics (min, max, avg, jitter, percentiles) for a target.

PING_TARGET="8.8.8.8" bash scripts/script.sh latency

compare

Compare connectivity and latency between multiple hosts side by side.

PING_TARGETS="8.8.8.8,1.1.1.1,208.67.222.222" bash scripts/script.sh compare

history

View stored ping history with optional filtering by target, date range, or status.

PING_TARGET="8.8.8.8" PING_LIMIT="20" bash scripts/script.sh history

export

Export ping history to CSV or JSON format.

PING_FORMAT="csv" PING_OUTPUT="ping_report.csv" bash scripts/script.sh export

config

View or update ping configuration (default count, timeout, interval).

PING_KEY="count" PING_VALUE="10" bash scripts/script.sh config

help

Show usage information and available commands.

bash scripts/script.sh help

version

Display the current version of the ping skill.

bash scripts/script.sh version

Environment Variables

VariableDescriptionDefault
PING_TARGETTarget host or IP address
PING_TARGETSComma-separated list of targets (for compare)
PING_COUNTNumber of ping packets to send4
PING_TIMEOUTTimeout in seconds per packet5
PING_INTERVALSeconds between pings (monitor mode)5
PING_DURATIONTotal monitoring duration in seconds60
PING_SUBNETCIDR notation subnet for sweep
PING_LIMITMax records to display in history50
PING_FORMATExport format: csv or jsonjson
PING_OUTPUTOutput file path for exportstdout
PING_KEYConfig key to set
PING_VALUEConfig value to set

Examples

# Quick connectivity check
PING_TARGET="google.com" bash scripts/script.sh check

# Monitor DNS server for 5 minutes
PING_TARGET="8.8.8.8" PING_INTERVAL="10" PING_DURATION="300" bash scripts/script.sh monitor

# Compare DNS providers
PING_TARGETS="8.8.8.8,1.1.1.1,9.9.9.9" bash scripts/script.sh compare

# Export last week's data as CSV
PING_FORMAT="csv" bash scripts/script.sh export

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...