← Back to Skills Marketplace
OpenClaw 维护脚本
by
jesson1222-ship-it
· GitHub ↗
· v0.1.0
411
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install openclaw-maintenance
Description
提供本地脚本监控和维护 OpenClaw Gateway,支持健康检测、代理切换、安全重启与日志清理,保障服务稳定运行。
Usage Guidance
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.
Capability Analysis
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.
Capability Assessment
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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-maintenance - After installation, invoke the skill by name or use
/openclaw-maintenance - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
OpenClaw 维护脚本合集 0.1.0
- 初始发布,收录所有基础维护脚本
- 支持 Gateway 健康监控与自动重启
- 提供代理网络健康检查和 VPN 节点切换
- 增加安全重启和日志自动清理功能
- 跨平台支持 macOS、Linux、NAS
- 提供详细安装、配置和使用说明
Metadata
Frequently Asked Questions
What is OpenClaw 维护脚本?
提供本地脚本监控和维护 OpenClaw Gateway,支持健康检测、代理切换、安全重启与日志清理,保障服务稳定运行。 It is an AI Agent Skill for Claude Code / OpenClaw, with 411 downloads so far.
How do I install OpenClaw 维护脚本?
Run "/install openclaw-maintenance" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is OpenClaw 维护脚本 free?
Yes, OpenClaw 维护脚本 is completely free (open-source). You can download, install and use it at no cost.
Which platforms does OpenClaw 维护脚本 support?
OpenClaw 维护脚本 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created OpenClaw 维护脚本?
It is built and maintained by jesson1222-ship-it (@jesson1222-ship-it); the current version is v0.1.0.
More Skills