Ayao Updater
v1.0.2Automatically updates OpenClaw and installed skills on a configurable schedule, handling package manager detection, local changes, and notifications.
⭐ 0· 103·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description match the actual behavior: the scripts call openclaw and clawhub to enumerate and update the platform and skills, handle local git changes, and notify the user. Minor inconsistencies in naming/pathing are present (SKILL.md and examples reference openclaw-auto-update, registry slug is ayao-updater, and smoke-test references a different folder), which looks like copy/paste sloppiness rather than malicious redirection.
Instruction Scope
Instructions and scripts stay inside the updater use-case: they read a JSON config (default location or overridden by OPENCLAW_UPDATE_CONFIG), call openclaw/clawhub, check git status of skill directories, write logs to /tmp, and (optionally) install a cron job. They do not embed network endpoints or attempt to read unrelated system files. The scripts will run commands that depend on external CLIs (openclaw, clawhub) — those binaries are executed with the privileges of the user running the updater, so trust in those CLIs is important.
Install Mechanism
No external install/downloads or archive extraction are present; this is an instruction-only skill with local shell scripts. install-cron.sh manipulates the user's crontab (expected for a scheduler) and logs to /tmp. No suspicious URLs or remote code fetching were found.
Credentials
No credentials or sensitive environment variables are requested. Optional environment overrides (OPENCLAW_UPDATE_CONFIG, OPENCLAW_WORKSPACE) are documented and reasonable. The scripts rely on the presence of openclaw, clawhub, python3, and bash, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not set always:true. It can install a persistent cron job (via install-cron.sh) which will run the updater on the schedule — this is expected for an auto-updater but is a persistent change to the user's crontab that the user must opt into. It writes logs to /tmp and invokes system commands (including optional gateway restart).
Assessment
This skill appears to do what it says: schedule and run OpenClaw and skill updates. Before installing, review and/or run the scripts manually in dry-run mode: 1) Inspect scripts/update.sh to confirm the notification target behavior and any command outputs you consider sensitive. 2) Run update.sh --dry-run to see planned actions; the script also supports a config file at ~/.openclaw/workspace/skills/openclaw-auto-update/config.json or a custom path via OPENCLAW_UPDATE_CONFIG. 3) The install script will modify your crontab and create a cron entry that runs the updater and writes to /tmp/openclaw-auto-update.log — if you do not want persistent scheduling, do not run install-cron.sh. 4) Ensure the openclaw and clawhub binaries on your machine are from trusted sources, because the updater will invoke them. 5) Note the minor naming/path inconsistencies in the files (ayao-updater vs openclaw-auto-update) — confirm you use the correct path when installing. If you want extra caution, run the smoke-test and review the output before enabling the cron job.Like a lobster shell, security has layers — review code before you run it.
latestvk9751jt0y1vm8r27n22v4bw90x837djw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.