ClawHub

Rr Reboot Report V2

v1.0.2

Detect unexpected system reboots and alert when the system comes back online. Tracks boot history and flags suspicious restarts.

⭐ 0· 53·0 current·0 all-time
by@elony-7
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (detect unexpected reboots and alert) align with the included scripts and runtime instructions. The only required binary is bash and the scripts operate on per-user state/config files under $HOME, which is appropriate for this purpose.
ℹ
Instruction Scope
SKILL.md and scripts read/write only a small set of home-directory files (~/.reboot-check-state, ~/.reboot-check-history, ~/.rr-reboot-config) and make network calls to api.telegram.org when configured. That behavior is within the stated purpose. Minor inconsistency: SKILL.md metadata lists a required config file (~/.rr-reboot-config) while the registry metadata earlier reported no required config paths; this is informational but not malicious.
✓
Install Mechanism
Instruction-only skill with bundled shell scripts and no install spec — nothing is downloaded or extracted at install time. Risk from install mechanism is low.
✓
Credentials
No environment variables or privileged credentials are requested by the skill. Telegram credentials are read from a user-created config file; asking only for BOT_TOKEN/CHAT_ID in that local file is proportional to the feature.
✓
Persistence & Privilege
The skill is not set always:true and does not request elevated or system-wide privileges. It writes per-user state files and recommends a user-managed @reboot cron entry; this is an expected and proportionate level of persistence for an auto-alert helper.
Scan Findings in Context
[no_findings] expected: Static pre-scan found no regex matches. For an instruction + shell-script skill this is expected; the behavior is visible in the provided scripts and aligns with the stated purpose.
Assessment
This skill appears coherent with its stated goal. If you plan to install it: 1) Review the two bundled scripts (they are short and readable). 2) If you enable automatic alerts, create ~/.rr-reboot-config yourself and set permissions to 600 so your bot token and chat ID stay private. 3) The scripts send only a short message with the boot time to api.telegram.org; confirm you trust using Telegram for alerts. 4) The scripts write state/history files under your home directory (~/.reboot-check-state and ~/.reboot-check-history) — if you need to avoid persistent files, run the checker manually instead of installing the cron @reboot. 5) Expect occasional false positives if system clock changes; test with --reset and --history before relying on alerts. If you want higher assurance, run the scripts as a non-root user or inspect and run them interactively before adding a cron entry.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cekvn38vxym9ap6e9jmy5jd83wfa4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🔄 Clawdis
Binsbash

Comments