Muguozi1 Openclaw Auto Updater
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill is an auto-updater as advertised, but it asks to create a persistent daily job that automatically changes the core agent and every installed skill without per-update approval.
Install only if you intentionally want unattended daily updates and trust the publisher and upstream package/skill registries. Safer use would be notification-only or dry-run first, then manual approval. If enabled, monitor summaries, keep backups, avoid privileged package-manager updates unless necessary, and confirm you can disable the cron job.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A future registry or package update could change how the agent behaves, break existing workflows, or install unsafe skill changes before the user reviews them.
The skill schedules high-impact tool actions that mutate the core agent and every installed skill, without requiring approval before each update run.
This skill sets up a daily cron job that: 1. Updates Clawdbot itself ... 2. Updates all installed skills (via `clawdhub update --all`)
Prefer a dry-run or notification-only default, require user approval before applying updates, and allow users to scope updates to specific trusted skills.
If an upstream package, registry entry, or skill update is compromised or faulty, this skill can automatically install it.
The documented routine pulls latest versions of the core agent and all skills from external package/skill sources, with no pinning, provenance checks, staged rollout, or rollback described.
npm update -g clawdbot@latest ... clawdbot doctor --yes ... SKILL_OUTPUT=$(clawdhub update --all 2>&1) || true
Pin trusted sources or versions where possible, review release notes before applying updates, and keep backups or rollback instructions for Clawdbot and skills.
The updater may keep changing the local agent environment daily until the cron job is removed or disabled.
The cron persistence is disclosed and central to the skill, but it means the agent will keep performing maintenance actions on a schedule after setup.
clawdbot cron add \ --name "Daily Auto-Update" \ --cron "0 4 * * *" \ --session isolated \ --wake now \ --deliver
Confirm the scheduled job after setup, monitor the delivered summaries, and know how to remove it with `clawdbot cron remove "Daily Auto-Update"`.
Users may overestimate the maturity or review status of a skill that can automatically update core agent code and all installed skills.
The bundled tests are placeholders that always pass, while the documentation claims strong test coverage and quality scores. Those trust signals are not well supported for a high-impact auto-updater.
# TODO: 添加实际测试
print("✓ PASSED")Do not rely on the quality badges alone; verify the publisher, source repository, and real test coverage before enabling unattended updates.