System Monitor OpenClaw
v1.0.1Monitor CPU, RAM, disk space, temperature, load average, and top processes on OpenClaw systems using a single versatile script.
⭐ 0· 516·4 current·4 all-time
by@aprilox
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (system CPU, RAM, disk, temp, top processes) matches the provided script and SKILL.md. The script uses standard system tools (top, free, df, ps, sensors/thermal_zone) consistent with a monitoring utility. Minor inconsistency: the registry metadata listed no required binaries, while SKILL.md metadata lists required bins (free, df, top, ps); this is a documentation mismatch but not a security issue.
Instruction Scope
SKILL.md instructs local installation and use of monitor.sh and documents optional lm-sensors for temperature — the runtime instructions are narrowly scoped to gathering local system metrics. The script reads only typical system locations (/proc via commands and /sys/class/thermal/thermal_zone0/temp) and runs local commands. It does not attempt to read unrelated files, transmit data over the network, or access secrets.
Install Mechanism
There is no automated install spec; this is an instruction-only skill with a single included script. No downloads or archive extraction are performed. Manual install steps are local (copy to workspace, chmod +x). Low install risk.
Credentials
The skill requires no environment variables, no credentials, and no config paths. The tools it expects (top, free, df, ps, optionally sensors) are proportionate to a monitoring tool. Nothing requests unrelated secrets or elevated external access.
Persistence & Privilege
The skill is not forced-always (always:false). disable-model-invocation is false (normal), meaning the agent could invoke the skill autonomously — appropriate for a utility. The skill does not modify other skills or system-wide settings.
Assessment
This skill appears to be a harmless local monitoring script. Before installing, verify the script content (monitor.sh) and confirm you are comfortable running it on your systems. Ensure the expected commands (free, df, top, ps) exist on target hosts and install lm-sensors only if you trust it and need temperature readings. Note the SKILL.md lists required binaries while the registry metadata did not — a minor documentation mismatch. Because the agent can invoke skills autonomously by default, consider whether you want the agent to run monitoring commands automatically; if not, disable autonomous invocation for this skill. If you need stronger guarantees, run the script in a limited environment (non-root user) and audit its behavior on a test machine first.Like a lobster shell, security has layers — review code before you run it.
latestvk970q4p7xatpm70zs63h3dg0en81n1j3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.