← Back to Skills Marketplace
370
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install system-maintenance-test
Description
Complete maintenance system for OpenClaw with unified architecture, filesystem governance, and cross-platform design
Usage Guidance
This skill promises system-level maintenance but the distributed package only contains SKILL.md and package.json — the actual scripts it tells you to run are not bundled and must be fetched from the GitHub repo or installed via bunx. Fetching and executing remote install scripts (one-click install) can run arbitrary commands with your user privileges and alter crontab, backups, and services. Before installing: (1) inspect the remote repository contents and open the install scripts to verify what they do; (2) check whether the install requires sudo or will modify system-critical files; (3) prefer running the install in a disposable VM/container or a staging machine first; (4) verify the GitHub repo owner, commit history, and issues for signs of trustworthiness; (5) if you need the skill but want lower risk, request the maintainer publish the scripts inside the skill bundle or provide an install spec with a vetted release tarball. If you cannot audit the scripts or trust the source, do not run the one-click install on production systems.
Capability Analysis
Type: OpenClaw Skill
Name: system-maintenance-test
Version: 1.3.2
The skill bundle describes a comprehensive system maintenance suite with high-privilege capabilities, including cron job modification, service management (pkill), and automated shell script execution (e.g., install-maintenance-system.sh, daily-maintenance.sh). While the stated intent is legitimate system upkeep, the broad permissions requested for filesystem governance and service recovery are inherently risky. Furthermore, the actual logic within the shell scripts and entry.js is not provided for verification, and the 'system-maintenance-test' slug suggests an experimental or non-production status.
Capability Assessment
Purpose & Capability
The SKILL.md describes a full maintenance system (cron jobs, backups, auto-recovery) which would legitimately require scripts that modify system state — that aligns with the stated purpose. However, the skill bundle itself only contains package.json and SKILL.md (no entry.js, no scripts/ directory), so the instructions assume fetching and executing code from the external GitHub repo or via bunx. That mismatch (declared project files absent from the package) is an incoherence and increases risk.
Instruction Scope
Runtime instructions explicitly tell the agent/user to git clone a remote repo and run install/maintenance shell scripts that change crontab, run monitoring, perform backups, and recover services. Those actions necessarily access/modify system files and could run arbitrary commands. While this scope is expected for a maintenance tool, the instructions grant broad discretion to fetch and execute remote scripts — the skill text also references integrations (webhooks, external log forwarding) which broaden the data paths.
Install Mechanism
There is no install spec in the package; instead SKILL.md recommends 'bunx clawhub@latest install system-maintenance' or cloning a GitHub repo and running bash scripts. Pulling and executing scripts from a remote repository (even GitHub) and running one-click install scripts is higher risk because the fetched scripts can perform any system action. The bundle's package.json references an entry.js main that is not present, amplifying the inconsistency.
Credentials
The registry metadata declares no required env vars or credentials, which is appropriate for a generic maintenance skill. However, the documentation lists integration points (Slack, webhooks, external log aggregation, Prometheus/Grafana) but does not declare any corresponding environment variables or credential requirements; if those features are used later they will likely require tokens/credentials, so there's a gap between claimed integrations and declared environment needs.
Persistence & Privilege
The skill is not marked 'always' and allows normal autonomous invocation. The installation instructions will create persistent system side-effects (cron jobs, backups, services) via shell scripts — this is expected for a maintenance tool but is a significant persistence/power footprint. Because the skill bundle doesn't include the scripts, the agent would fetch and run external code to obtain that persistence.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install system-maintenance-test - After installation, invoke the skill by name or use
/system-maintenance-test - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.2
- Reorganized SKILL.md for easier navigation with a layered, progressive disclosure format.
- Enhanced documentation for installation, architecture, configuration, and usage examples.
- Consolidated backup and rollback instructions; included clear command references.
- Cleaned up legacy backup file documentation.
- No changes to core functionality announced in this version.
Metadata
Frequently Asked Questions
What is System Maintenance Test?
Complete maintenance system for OpenClaw with unified architecture, filesystem governance, and cross-platform design. It is an AI Agent Skill for Claude Code / OpenClaw, with 370 downloads so far.
How do I install System Maintenance Test?
Run "/install system-maintenance-test" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is System Maintenance Test free?
Yes, System Maintenance Test is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does System Maintenance Test support?
System Maintenance Test is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created System Maintenance Test?
It is built and maintained by jazzqi (@jazzqi); the current version is v1.3.2.
More Skills