OpenClaw 沙盒测试系统

OpenClaw 沙盒测试系统 v2.0 - 零风险配置变更测试，9 层防护 +5 原则，自动备份回滚，Git 版本管理

This skill appears to implement a useful sandbox workflow for OpenClaw, but review the scripts before running them. Specifically: 1) Inspect templates/safe-try.sh and templates/apply-config.sh to ensure the openclaw commands, ports, and the sandbox token are acceptable for your environment. 2) Remove or change the enabled plugin ('feishu-openclaw-plugin') if you don't want sandbox to load external integrations — that plugin may need credentials not declared by the skill. 3) Fix the hard-coded user path in scripts/cleanup-env.sh (/Users/wh1ko) — it will mis-restore HOME on other machines; prefer restoring HOME from the parent shell or documenting the expected username. 4) Run the sandbox first on an isolated test machine or non-critical account, confirm the backup/rollback process works, and only then use apply-config.sh on production. 5) Because the scripts start a background gateway, ensure you understand how to stop it (PID file location) and verify logs before applying changes to production.

Type: OpenClaw Skill Name: openclaw-sandbox Version: 2.0.0 The skill bundle provides a sandbox for OpenClaw configuration testing but contains high-risk environment manipulation and poor portability. Specifically, `scripts/cleanup-env.sh` hardcodes a specific developer's path (`/Users/wh1ko`) and attempts to force the `$HOME` variable to it, which would disrupt the shell environment for any other user. While the scripts in `templates/` include backup and validation logic, the aggressive modification of core environment variables and the execution of background processes via `nohup` in `templates/safe-try.sh` represent risky behaviors that could lead to system instability if used outside the original developer's specific environment.