← Back to Skills Marketplace
satoshistackalotto

System Health Check

by Stems · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
689
Downloads
0
Stars
5
Active Installs
1
Versions
Install in OpenClaw
/install system-health-check
Description
System health validator — checks skill files, paths, permissions, binaries, backup freshness, and encryption. Produces pass/fail reports.
Usage Guidance
Before installing or enabling this skill, ask the maintainer to clarify the contradictions: (1) does the tool truly run read-only, or will it create reports/log entries under OPENCLAW_DATA_DIR (which implies writes)? (2) why does EVALS.json expect 'curl' while the skill metadata does not list curl as required? (3) what exactly do the 'encryption' and 'integrity' checks read or require (any secrets or privileged access)? If you plan to run it, test in a non-production environment first, inspect what files it actually creates when run with different flags (especially --save-report), and ensure your agent's ability to auto-invoke the skill is constrained if you do not want automated writes to your data directory.
Capability Analysis
Type: OpenClaw Skill Name: system-health-check Version: 0.1.0 The 'system-health-check' skill is a diagnostic tool designed to validate the integrity and configuration of the OpenClaw Greek Accounting system. Both SKILL.md and EVALS.json explicitly state and consistently reinforce that the skill is 'Read-only' and 'Never modifies any data.' It checks for file presence, directory structure, permissions, dependencies, backup freshness, process locks, and encryption status, reporting issues without taking any corrective actions itself. Remediation commands are provided as descriptive strings in the output, not as executable instructions for the agent. There is no evidence of intentional harmful behavior, data exfiltration, malicious execution, or persistence mechanisms. The described checks, while involving file system and environment variable access, are entirely consistent with its stated purpose as a non-destructive health validator.
Capability Assessment
Purpose & Capability
Name/description (system health validator for OpenClaw) align with requiring openclaw, jq, and OPENCLAW_DATA_DIR. openssl for hash checks is reasonable. However the EVALS.json expectations mention verifying 'curl' is installed while the declared required binaries do not include curl, and counts for expected skill/EVAL files are inconsistent (expected_count:20 vs narrative '19 operational skills + canonical map'). These mismatches are minor but unexplained.
Instruction Scope
SKILL.md repeatedly claims 'read-only' and 'never modifies any data' but also documents features that write or log data: --save-report (writes to /data/reports/system/), EVALS expectations that failures are logged to /data/memory/failures/, and example remediation advice that implies state changes by operators. The instructions instruct reading many sensitive paths under $OPENCLAW_DATA_DIR (expected), but the read-only promise conflicts with documented report/log writing and is not reconciled in the documentation. The 'encryption status' and 'integrity' checks are underspecified (unclear if they require keys or privileged reads).
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. Nothing is downloaded or extracted by the skill itself.
Credentials
Only OPENCLAW_DATA_DIR and availability of jq/openssl/openclaw are required — this is proportionate for a health-checker that scans the OpenClaw data tree. No secrets or unrelated credentials are requested. Minor discrepancy: EVALS.json expects curl to be verified but curl is not declared as required.
Persistence & Privilege
The skill is not forced-always and is user-invocable (normal). However the documentation implies it can write reports/logs under $OPENCLAW_DATA_DIR (e.g., --save-report and logging failures), contradicting the 'read-only' promise. If allowed to run autonomously by the agent, that write behavior could create data the user did not expect. Clarification is needed about what the skill will write by default and whether any writes require explicit flags or elevated permissions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install system-health-check
  3. After installation, invoke the skill by name or use /system-health-check
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of the system-health-check skill for OpenClaw Greek Accounting. - Validates skill file presence, integrity, and test coverage across all skills. - Checks directory structure and flags any non-canonical paths under `/data/`. - Verifies sensitive directory and file permissions for security compliance. - Ensures required binaries and environment variables are set for operation. - Reports on backup freshness, file encryption status, and process locks. - Provides clear pass/fail reports with actionable remediation steps. - Designed for safe, read-only, cron-friendly daily or pre-operation use.
Metadata
Slug system-health-check
Version 0.1.0
License
All-time Installs 8
Active Installs 5
Total Versions 1
Frequently Asked Questions

What is System Health Check?

System health validator — checks skill files, paths, permissions, binaries, backup freshness, and encryption. Produces pass/fail reports. It is an AI Agent Skill for Claude Code / OpenClaw, with 689 downloads so far.

How do I install System Health Check?

Run "/install system-health-check" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is System Health Check free?

Yes, System Health Check is completely free (open-source). You can download, install and use it at no cost.

Which platforms does System Health Check support?

System Health Check is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created System Health Check?

It is built and maintained by Stems (@satoshistackalotto); the current version is v0.1.0.

💬 Comments