Update Approval Guard

Use this skill when the user wants scheduled update checks for OpenClaw and installed skills, but does not want automatic mutation. The skill performs dry-ru...

This skill's behavior (check-only then apply after explicit approval) is reasonable, but the provided bundle contains many unrelated scripts, other skills, and hard-coded tokens. Before installing: 1) Inspect publish.sh and do not run it unless you trust it — it may git-init and push code. 2) Search the package for hard-coded secrets (app tokens, API keys) and remove/rotate any you find. 3) Verify cron job creation is performed in an isolated session and that the scheduled job cannot leak workspace files or push to external repos. 4) Review AGENTS.md/SOUL.md behavior: they instruct agents to read memory and user files — ensure that scheduled checks won’t expose sensitive memory to external channels. 5) If you only want the update-check logic, extract and install just the SKILL.md and example cron payload (avoid running publish scripts and unrelated code). If you’re unsure, test in a sandbox workspace (no real credentials) or decline installation until the package is cleaned.

Type: OpenClaw Skill Name: update-approval-guard Version: 1.0.0 The bundle contains numerous hardcoded sensitive credentials, including Feishu App Secrets (e.g., in `skills/feishu-calendar-v2/scripts/calendar.sh`), Tavily API keys (`scripts/daily_report.py`), and Bearer tokens in configuration files (`config/mcporter.json`). It also includes scripts with high-risk capabilities, such as `skills/veadk-skills/scripts/save_file.py` which allows arbitrary file writes, and `skills/hiic-industry-daily-report/scripts/schedule-push.sh` which modifies the system crontab. While these represent significant security vulnerabilities and poor credential management, they appear to be part of a complex, functional workspace rather than intentionally malicious code designed for data exfiltration or unauthorized remote control.