SKILLEMALL.ai
GitHub ↗ RU Sign in

CC system-healthcheck

Three-tier system health monitoring (L1/L2/L3) with heartbeat mechanism. Zero external dependencies, i18n support, console output only.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: Carlos J Cabrales III v1.0.0 MIT-0 20 files · 1 script body ≈ 818 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 57/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
72/100
safety, quality, tests
Safety 60%
72
Quality 40%
72
Run on models
none yet
Process rating
C
57/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: system-healthcheck (ClawHub)

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 11

  • high Dangerous commands cmd-persistence INSTALL.md:142
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    sudo launchctl load -w /System/Library/LaunchDaemons/com.vix.cron.plist
Medium and low: 10
  • low Dangerous commands cmd-cron-mention DEVELOPMENT_SUMMARY.md:175
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention INSTALL.md:49
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention INSTALL.md:71
    Mentions editing / listing crontab
    crontab -l
  • low Dangerous commands cmd-background-process INSTALL.md:139
    Starts a background / autostarted process
    sudo systemctl enable cron
  • low Dangerous commands cmd-cron-mention INSTALL.md:163
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention PUBLISHED.md:85
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention README.md:86
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention README.zh-CN.md:54
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention SKILL.md:70
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention templates/crontab_example.txt:4
    Mentions editing / listing crontab (test fixture / example file)
    # 1. 编辑 crontab: crontab -e
    fixture

Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 57/100

  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (system-healthcheck) differs from the folder (cc3po-system-healthcheck)
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 17 steps
  • 100Execution cost. Instruction body is 818 tokens
  • 100Running it twice. No mutating operations
  • low 12 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • -32 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 135: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 17 items
  • +3Output format is stated explicitly
  • +4Has examples (12 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: clean
This skill is a local system health monitor, and its broader host checks are consistent with that purpose when users knowingly enable them.
LLM: benign (high) · VirusTotal: · 29 May 2026