ping-monitor

What This Skill Does

The ping-monitor skill serves as a fundamental diagnostic utility within the OpenClaw ecosystem, designed to perform ICMP (Internet Control Message Protocol) health checks. By leveraging the system-native ping utility, this skill allows the AI agent to verify the network reachability of various endpoints, including remote servers, office VoIP phones, and local background daemons. It abstracts away the command-line complexity, enabling the agent to confirm connectivity status in real-time. Whether you need to troubleshoot a drop in network performance or automate the monitoring of infrastructure uptime, this skill provides the necessary feedback to make informed decisions about service availability.

Installation

This skill is pre-configured for environments where the ping utility is available. To install it into your agent instance, use the following command:

clawhub install openclaw/skills/skills/xejrax/ping-monitor

Once installed, the agent will have immediate access to the ping-monitor command without requiring further configuration or external dependencies.

Use Cases

• Infrastructure Monitoring: Automatically verify if critical servers are responding before triggering more complex tasks.
• VoIP Troubleshooting: Quickly identify if office desk phones have lost connectivity to the local network or internet.
• Connectivity Debugging: Use the agent to troubleshoot intermittent latency or total packet loss for specific network segments.
• Daemon Health: Ensure that specific network-listening processes or daemons are alive and responding to ICMP packets.

Example Prompts

1. "Ping the production database server at 192.168.1.50 to see if it is currently online."
2. "Can you check the network connectivity for the phone in the conference room at 10.0.0.15 using 3 packets?"
3. "Is the mail server responding? Run a ping-monitor check on mail.internal.corp."

Tips & Limitations

• Permissions: Depending on the host OS security policies, the agent process may require specific privileges to execute raw ICMP packets. Ensure the environment allows standard ping operations.
• Latency vs. Availability: Keep in mind that ping results measure ICMP reachability; a successful ping does not necessarily mean an application or service (like a web server or database) is functioning correctly—it only proves the host is reachable at the network layer.
• Firewall Interference: Many modern security appliances drop ICMP packets by design. If you receive a timeout error, it may be due to a firewall policy rather than a genuine hardware failure.