← Back to Skills Marketplace
lookupmark

System Monitor

by LookUpMark · GitHub ↗ · v1.3.0 · MIT-0
cross-platform ⚠ suspicious
121
Downloads
0
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install lookupmark-system-monitor
Description
Monitor system health on the gateway host (Raspberry Pi / ARM / Linux). Reports CPU, RAM, disk, temperature, uptime, load, top processes. Can check alert thr...
README (SKILL.md)

System Monitor

Real-time system health monitoring for the gateway host. Zero external dependencies.

Usage

# Full status report (human-readable)
python3 scripts/monitor.py

# JSON output (for programmatic use)
python3 scripts/monitor.py --json

# Check alert thresholds
python3 scripts/monitor.py --check-alerts

# Top N processes
python3 scripts/monitor.py --top 10

What It Reports

Metric Source
CPU usage % /proc/stat
RAM used/total/available /proc/meminfo
Swap used/total /proc/meminfo
Disk usage per mount df -h
CPU temperature /sys/class/thermal/thermal_zone0/temp
Uptime /proc/uptime
Load average (1/5/15m) /proc/loadavg
Top processes by CPU ps aux

Alert Thresholds

Default (configurable in SKILL.md or via code):

Alert Threshold
RAM > 90% used
Swap > 500MB used
CPU temp > 75°C
Disk > 90% full

Security

  • Read-only: Never writes, modifies, or executes anything beyond reading system stats
  • No network access: Purely local /proc, /sys, ps, df
  • No secrets: Does not access config files, tokens, or credentials
  • Safe in groups: Output contains no sensitive paths, tokens, or user data

Automation

Use with cron for periodic health checks:

# Every 30 minutes via OpenClaw cron → alerts to Telegram
# Or via HEARTBEAT.md
Usage Guidance
This skill appears to do what it says (local system health checks), but review these before installing: - The script reads ~/.config/system-monitor/config.json (not declared in metadata). Inspect that file's contents/permissions if it exists. - Process command lines are reported (sanitized for common token patterns), but the redaction is pattern-based and can miss secrets passed as positional arguments or stored in environment variables. If you run this on hosts with sensitive command-line arguments, consider restricting its use or limiting --top output. - The SKILL.md claims 'no sensitive output' — treat that as optimistic. Expect mount points and trimmed commands in outputs. - The script is local and read-only (no network), and there is no installer. If you need stronger guarantees, run it in a non-sensitive account or inspect/modify the code to suit your security policy. If you want me to, I can suggest small code changes to harden redaction or to avoid reading the config file by default.
Capability Analysis
Type: OpenClaw Skill Name: lookupmark-system-monitor Version: 1.3.0 The system-monitor skill is a standard utility for reporting host health metrics (CPU, RAM, disk, temperature) on Linux/ARM systems. The implementation in scripts/monitor.py is well-structured, uses safe subprocess calls with argument lists to prevent shell injection, and includes a proactive security feature (sanitize_cmdline) to redact potential secrets like tokens or passwords from the process list. No network activity, data exfiltration, or malicious instructions were identified.
Capability Tags
crypto
Capability Assessment
Purpose & Capability
The name/description match the code: it reads /proc, /sys, calls ps and df, and reports CPU, RAM, disk, temp, uptime and top processes. This behavior is expected for a system-monitor. Minor inconsistency: the SKILL.md header mentions vcgencmd but the script does not call it.
Instruction Scope
Runtime instructions are local and read-only; the script does not perform network calls or require external services. However the SKILL.md claims 'Safe in groups: Output contains no sensitive paths, tokens, or user data' — the script does include mount points and truncated process command lines which can contain sensitive info. The script attempts to sanitize common token/key patterns, but that redaction is pattern-based and not exhaustive.
Install Mechanism
No install spec (instruction-only with an included script). Nothing is downloaded or written by an installer.
Credentials
Metadata declared 'Required config paths: none', but the script reads a per-user config at ~/.config/system-monitor/config.json to load thresholds. No env vars or credentials are requested. Reading a user config folder is reasonable for thresholds, but the mismatch between metadata and actual config access should be noted.
Persistence & Privilege
always is false and the skill does not modify other skills or system settings. It only reads system state and a single per-user config file.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lookupmark-system-monitor
  3. After installation, invoke the skill by name or use /lookupmark-system-monitor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
Removed duplicate code, sanitize process command lines
v1.2.0
Fixed broken main() function. Config-based thresholds.
v1.1.0
Configurable alert thresholds via config file.
v1.0.0
Initial release. CPU, RAM, disk, temp, uptime, load, top processes. Alert thresholds. Zero deps.
Metadata
Slug lookupmark-system-monitor
Version 1.3.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 4
Frequently Asked Questions

What is System Monitor?

Monitor system health on the gateway host (Raspberry Pi / ARM / Linux). Reports CPU, RAM, disk, temperature, uptime, load, top processes. Can check alert thr... It is an AI Agent Skill for Claude Code / OpenClaw, with 121 downloads so far.

How do I install System Monitor?

Run "/install lookupmark-system-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is System Monitor free?

Yes, System Monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does System Monitor support?

System Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created System Monitor?

It is built and maintained by LookUpMark (@lookupmark); the current version is v1.3.0.

💬 Comments