← 返回 Skills 市场
jesson1222-ship-it

OpenClaw 维护脚本

作者 jesson1222-ship-it · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
411
总下载
0
收藏
2
当前安装
1
版本数
在 OpenClaw 中安装
/install openclaw-maintenance
功能描述
提供本地脚本监控和维护 OpenClaw Gateway,支持健康检测、代理切换、安全重启与日志清理,保障服务稳定运行。
安全使用建议
This package's scripts do what the README says (monitor health, restart the gateway, switch Clash proxies, clean logs), but note two issues before installing: 1) the registry metadata does not declare the sensitive environment variables the scripts expect — you must provide OPENCLAW_NOTIFY_TARGET and, if using proxy switching, CLASH_API and CLASH_SECRET; 2) the scripts will invoke your local openclaw CLI to restart the gateway and will make network calls (to the local Clash API and to a public URL used for latency tests). Before installing, review and verify: the .env.example contents, the hard-coded OPENCLAW_BIN path (/opt/homebrew/bin/openclaw), what the openclaw CLI does and what credentials it stores, and that your Clash API is local and trusted. If you plan to deploy as a service (systemd/LaunchAgent), inspect or create the service/Plist files yourself rather than blindly loading unreviewed units. If you cannot audit or trust these scripts, avoid running them as-is or run them in a controlled environment (test machine/container) first.
功能分析
Type: OpenClaw Skill Name: openclaw-maintenance Version: 0.1.0 The bundle provides a suite of maintenance scripts for OpenClaw, including automated service monitoring and restarts (gateway-watchdog.sh), log file deletion (cleanup-logs.sh), and network proxy switching via the Clash API (proxy-health.sh). While the code is well-documented and the logic is consistent with the stated purpose of system maintenance, the scripts utilize high-risk capabilities such as service manipulation, file system modification, and network configuration changes. No evidence of malicious intent, data exfiltration, or obfuscation was found, but the broad permissions required for these operations warrant a suspicious classification per the provided criteria.
能力评估
Purpose & Capability
The code and SKILL.md align with the stated purpose (gateway health checks, safe restarts, proxy switching via a local Clash API, log cleanup). However the registry metadata declares no required environment variables or credentials while the instructions and scripts clearly require and use sensitive variables (e.g., OPENCLAW_NOTIFY_TARGET, CLASH_API, CLASH_SECRET, OPENCLAW_BIN). This mismatch is unexpected and worth noting.
Instruction Scope
Runtime instructions and scripts stay within the maintenance domain: they check a health endpoint, call the local Clash API, switch proxies, invoke the local openclaw CLI to restart/start/stop the gateway, write logs under ~/.openclaw, and manage a /tmp lock file. There are network calls (to local Clash API and to external DELAY_TEST_URL defaulting to api.telegram.org for latency tests) and a notification path that uses the openclaw CLI to send Telegram messages. The scope is narrowly focused on maintenance and monitoring; no unrelated system file reads or remote code downloads are triggered by the scripts themselves.
Install Mechanism
No remote install steps or downloads are present; install.sh simply copies bundled .sh files to ~/.openclaw/scripts and makes them executable. This is low-risk from an installation mechanism standpoint (no external archives or URLs executed).
Credentials
The package metadata lists no required env vars, but SKILL.md and the scripts require sensitive configuration: OPENCLAW_NOTIFY_TARGET (Telegram ID), optional CLASH_API and CLASH_SECRET (API bearer token), OPENCLAW_BIN, and other parameters. These are proportional to the claimed functionality, but the omission from metadata is an incoherence and increases risk because users may not realize they need to supply secrets. The scripts also invoke the local openclaw CLI which may itself have credentials or permissions — users should verify what that CLI does and what privileges it holds.
Persistence & Privilege
The skill is not always:true and does not attempt to modify other skills or system-wide settings beyond copying files under the invoking user's home directory and recommending systemd/LaunchAgent usage. It uses /tmp for a lock file and writes logs to ~/.openclaw/logs. It will, when executed, restart services (via openclaw CLI) and control a local Clash API if configured — those are expected side effects for a watchdog but are privileged operational actions that require user consent.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install openclaw-maintenance
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /openclaw-maintenance 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.1.0
OpenClaw 维护脚本合集 0.1.0 - 初始发布,收录所有基础维护脚本 - 支持 Gateway 健康监控与自动重启 - 提供代理网络健康检查和 VPN 节点切换 - 增加安全重启和日志自动清理功能 - 跨平台支持 macOS、Linux、NAS - 提供详细安装、配置和使用说明
元数据
Slug openclaw-maintenance
版本 0.1.0
许可证
累计安装 3
当前安装数 2
历史版本数 1
常见问题

OpenClaw 维护脚本 是什么?

提供本地脚本监控和维护 OpenClaw Gateway,支持健康检测、代理切换、安全重启与日志清理,保障服务稳定运行。 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 411 次。

如何安装 OpenClaw 维护脚本?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install openclaw-maintenance」即可一键安装,无需额外配置。

OpenClaw 维护脚本 是免费的吗?

是的,OpenClaw 维护脚本 完全免费(开源免费),可自由下载、安装和使用。

OpenClaw 维护脚本 支持哪些平台?

OpenClaw 维护脚本 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 OpenClaw 维护脚本?

由 jesson1222-ship-it(@jesson1222-ship-it)开发并维护,当前版本 v0.1.0。

💬 留言讨论