System Healthcheck
v1.0.1Three-tier system health monitoring (L1/L2/L3) with heartbeat mechanism. Zero external dependencies, i18n support, console output only.
⭐ 1· 110·0 current·0 all-time
bylim@lim1202
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (three-tier health checks, heartbeat, i18n, console output) match the shipped scripts: l1/l2/l3/heartbeat and i18n; required tools (systemctl/pgrep/lsof) and reading local files are appropriate for a monitoring tool.
Instruction Scope
Runtime instructions and scripts operate on local system state (workspace files like SOUL.md, /proc/meminfo, systemctl/pgrep/lsof). This is within the stated purpose, but INSTALL.md suggests adding an automatic L1 invocation into OpenClaw's session init and configuring crontab — these are legitimate for monitoring but will cause the agent/host to run checks automatically and require the user to edit host configuration.
Install Mechanism
No install spec is provided (instruction-only), installation is via clawhub or manual git clone as documented. No remote installers, URL shorteners, or archive extraction are used in the metadata.
Credentials
The skill requests no credentials or privileged environment variables. It optionally reads OPENCLAW_LOCALE and uses common environment vars for PATH/personal dirs in crontab examples; these are proportional to i18n and local configuration.
Persistence & Privilege
The skill does not request 'always:true' or modify other skills, but documentation instructs adding crontab entries and (optionally) injecting an L1 subprocess call into OpenClaw session initialization. Those changes give it persistent automatic execution on the host if the user applies them — expected for a healthcheck but worth user awareness.
Assessment
This package appears coherent for local health monitoring, but review and sanity-check before installing: 1) Inspect the scripts (they run local commands, read ~/.openclaw/workspace files and /proc, and call system utilities like systemctl/pgrep/lsof). 2) Run ./scripts/test.sh manually in a safe environment first (non-production) to see outputs. 3) If you don't want automatic runs, do NOT add the suggested code to your OpenClaw session-init or crontab; instead run checks manually. 4) No network endpoints or secrets are requested, but verify you trust the source before cloning into ~/.openclaw/skills. 5) Optional: audit the l2/l3 scripts (full l3 content truncated in scan) if you need assurance they don't execute unexpected commands on your system.Like a lobster shell, security has layers — review code before you run it.
latestvk971xjkb2y9psqbezr1b0y8s4s83f2zd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.