system-uptime

What This Skill Does

The system-uptime skill provides OpenClaw agents with the ability to query the operational duration of the host machine. By leveraging the native Unix uptime command, the skill retrieves the precise amount of time the system has been continuously active since its last reboot, along with the current time, the number of active users, and system load averages. This data is essential for maintaining awareness of system health and stability, allowing the agent to provide immediate feedback on how long the environment has been running without interruption.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface. Ensure you have the necessary permissions to install extensions in your workspace. Execute the following command in your terminal:

clawhub install openclaw/skills/skills/alamby/system-uptime

Once installed, the agent will automatically detect and register the skill, enabling it to process user requests regarding system status immediately.

Use Cases

This skill is primarily designed for administrative monitoring and quick diagnostic checks. It is highly effective for developers or system administrators who need to verify if a recent patch or configuration change triggered a reboot, or to check for signs of long-term system stress through load averages. It acts as a primary entry point for health diagnostics before moving on to more complex monitoring tools.

Example Prompts

1. "How long has the system been running since the last reboot?"
2. "Can you check the current uptime and system load for me?"
3. "Is the server status healthy? Show me the uptime."

Tips & Limitations

While the system-uptime skill is excellent for high-level status checks, it has specific constraints to keep in mind. It does not provide historical logs or reboot patterns; for audit trails, you should query /var/log or equivalent system files. Additionally, this skill is restricted to the host machine where the OpenClaw agent is currently running. If you require uptime data for a remote server, you must provide the agent with the appropriate network connectivity or use specialized remote monitoring tools. Because the output of uptime can vary slightly between Unix-like operating systems (such as differences in date formatting between Linux and macOS), ensure your downstream data parsing is robust enough to handle these minor variations.