SKILLEMALL.ai
RU Sign in

BF system-maintenance

Complete maintenance system for OpenClaw with unified architecture, filesystem governance, and cross-platform design

ClawHub Agent Skills author: jazzqi v1.3.2 MIT-0 3 files body ≈ 1 692 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process F 38/100 · Will not run — References files that are not bundled: scripts/config.json

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
B
84/100
safety, quality, tests
Safety 60%
99
Quality 40%
61
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: scripts/config.json
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ClawHub

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-cron-mention SKILL.md:49
    Mentions editing / listing crontab
    crontab -l | grep -i openclaw

Files scanned: 3. 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")
  • warning missing-ref reference to a missing file: scripts/config.json

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: scripts/config.json
  • 0Tools and files. 1 referenced file(s) missing: scripts/config.json
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (system-maintenance) differs from the folder (system-maintenance-test)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 39 steps
  • 100Execution cost. Instruction body is 1692 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Description length 116: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -219 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 39 items
  • +4Has examples (12 code blocks)

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

External checks

ClawHub: suspicious
This maintenance skill has a plausible purpose, but it asks users to run unreviewed external maintenance scripts that can create recurring jobs, change files, restore backups, and restart services without clear safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026