SKILLEMALL.ai
GitHub ↗ RU Sign in

BB deadmans-switch

Self-healing infrastructure guardian. Monitors services, diagnoses failures, executes recovery playbooks, and learns from incidents.

ClawHub Agent Skills author: peres84 v0.1.0 MIT-0 6 files body ≈ 1 348 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 69/100 · Nearly there — weak spots: inputs and preconditions

ProcedureInfrastructuretype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
75
Run on models
none yet
Process rating
B
69/100
Nearly there
Inputs and preconditions w 11
0
Tools and files w 18
60
Result and completion w 14
60
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 Dangerous commands cmd-privilege playbooks/disk.md:66
    Privilege escalation / world-writable permissions (documentation of a security skill)
    sudo rm -rf /var/lib/apt/lists/*
    security skill

Files scanned: 6. 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 69/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 60Tools and files. Uses tools (read) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 28 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1348 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 132: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 28 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: suspicious
This appears to be a legitimate infrastructure repair skill, but it can make powerful automatic system changes that users should review before installing.
LLM: suspicious (high) · VirusTotal: · 28 May 2026