Auto Updater Gateway
Analysis
This skill is transparent about being an auto-updater, but it creates a persistent daily job that can update every installed ClawHub skill and send reports externally without per-update review.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`npx clawhub update --all` ... `Update all installed ClawHub skills`
The documented workflow bulk-updates every installed skill, which changes the agent's supply chain without an allowlist, version pinning, or review step described in the artifacts.
openclaw cron add ... --cron "0 4 * * *" ... --wake now
The setup creates a persistent scheduled job that wakes and runs daily, so the updater continues operating after the initial setup.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Logged into ClawHub: `npx clawhub login` ... Verify token is valid: `npx clawhub whoami`
The cron workflow relies on the user's local authenticated ClawHub CLI session to perform updates.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
--deliver --channel feishu --to "ou_xxxxxxxxxxxx" ... Deliver to configured channel (Feishu/Telegram)
The skill sends update reports to an external messaging channel, including version comparison details.
