SKILLEMALL.ai

BC sunny-health-monitor

Lightweight system health monitoring for macOS - monitor CPU, memory, disk usage, cron job status, and generate health reports with Discord notifications.

ClawHub Agent Skills author: LuckPoppy v1.0.0 MIT-0 5 files body ≈ 1 009 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorDiscordInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
66
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url scripts/monitor.cjs:25
    Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
    'https://discord.com/api/webhooks/1481951256879693866/NQdb…zKP'
    vendor-hostquoted

Files scanned: 5. 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")
  • note frontmatter-key unknown frontmatter key "keywords"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 100Tools and files. No external tools needed
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1009 tokens
  • 100Running it twice. No mutating operations
  • low 11 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)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -258 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 154: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (10 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This health monitor broadly does what it claims, but it can send local system and OpenClaw cron status information to a hardcoded Discord webhook by default.
LLM: suspicious (high) · VirusTotal: suspicious · 27 May 2026