BC vps-guardian
Autonomous VPS monitoring and auto-remediation — kills runaway procs, frees disk, restarts dead services, hardens security. Not alerts. Action.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Dangerous commands
cmd-privilegeskill-card.md:22Privilege escalation / world-writable permissions (documentation of a security skill)Risk: The documented sudo curl install path is unpinned and may fetch changed code. <br>
security skill -
low Dangerous commands
cmd-privilegeSKILL.md:29Privilege escalation / world-writable permissions (documentation of a security skill)sudo curl -o /usr/local/bin/vps-guardian https://raw.githubusercontent.com/vps-guardian/guardian/main/src/guardian.py
security skill -
low Dangerous commands
cmd-privilegeSKILL.md:30Privilege escalation / world-writable permissions (documentation of a security skill)sudo chmod +x /usr/local/bin/vps-guardian
security skill -
low Dangerous commands
cmd-privilegeSKILL.md:33Privilege escalation / world-writable permissions (documentation of a security skill)sudo cp /usr/local/bin/vps-guardian.conf.example /etc/vps-guardian.conf
security skill
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 143 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1196 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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
- +1No license
- +2Single-language instructions
- +3Description length 143: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: suspicious
This is a coherent VPS self-healing tool, but it gives an agent broad unattended root-level power to alter a live server with inconsistent approval safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026