Reboot Checker
v1.0.0Detect unexpected system reboots and alert when the system comes back online. Tracks boot history and flags suspicious restarts.
⭐ 0· 80·0 current·0 all-time
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 (detect unexpected reboots) matches the included script and instructions. Minor mismatch: metadata declares only 'bash' as a required binary, but the script also invokes who, awk, uptime, stat, date, and cut — common on most systems but not explicitly declared.
Instruction Scope
SKILL.md instructs running the bundled script, viewing history, and resetting state. The script only reads system boot time and writes to user-scoped state/history files; it does not contact external endpoints or read unrelated system data.
Install Mechanism
No install spec (instruction-only plus a script file). Nothing is downloaded or installed automatically; the script is executed locally. This is low-risk from an install perspective.
Credentials
No environment variables, credentials, or external tokens are requested. The script uses HOME (normal) and supports overriding file paths via --state / environment variables STATE_FILE/HISTORY_FILE, which is reasonable for flexibility.
Persistence & Privilege
The script persists state/history in ~/.reboot-check-state and ~/.reboot-check-history by default. Note: the --state option (or setting STATE_FILE env var) can point to any writable path and the script will overwrite that file, so running this as root could overwrite arbitrary files — use non-root contexts or carefully choose state paths.
Assessment
This skill appears to do exactly what it claims: a local helper that records boot timestamps and signals reboots. It does not request network access or secrets. Before installing/running: (1) review and, if needed, adjust the default state/history paths; avoid running it as root to prevent accidental overwrites of sensitive files (the --state option can write to any path the process can write to); (2) ensure the host has the standard utilities the script uses (who, awk, uptime, stat, date); and (3) if you plan to run it from cron or a system-wide context, set explicit file paths and ownership so logs/state are written where you expect. Overall the skill is coherent and low-risk when used with those precautions.Like a lobster shell, security has layers — review code before you run it.
latestvk97cwwn0ymzt8kmwce29cwskas83v43b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔄 Clawdis
Binsbash