SKILLEMALL.ai

BC aegis-protocol

Self-healing stability monitor for AI agents - 5 core checks + 15 extended checks, auto-recovery, health scoring

ClawHub Agent Skills author: ankechenlab-node v0.12.9 MIT-0 18 files body ≈ 572 tokens Open the sourceclawhub.ai analyzed 2 d ago

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

ReferenceInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
94
Quality 40%
68
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 · 6

✓ No critical or high findings

Medium and low: 6
  • low Dangerous commands cmd-cron-mention aegis-protocol.py:419
    Mentions editing / listing crontab (string literal in code, not executed)
    code, out, err = exec_cmd("crontab -l 2>&1")
    code literal
  • low Dangerous commands cmd-cron-mention CLAWHUB_ISSUE_TEMPLATE.md:50
    Mentions editing / listing crontab
    crontab -l
  • low Dangerous commands cmd-cron-mention README.md:265
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention SECURITY_AUDIT.md:27
    Mentions editing / listing crontab (documentation table row; documentation of a security skill)
    | `crontab -l` | 检查 cron 任务 | ✅ 无风险 |
    tablesecurity skill
  • low Risky intent intent-offensive-security SECURITY.md:66
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - ❌ No credential harvesting
  • low Dangerous commands cmd-cron-mention SECURITY.md:117
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -l                # Cron jobs
    security skill

Files scanned: 15. 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 "security-note"

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. Tools declared in frontmatter
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 572 tokens
  • 100Running it twice. No mutating operations

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 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (3 code blocks)

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

External checks

ClawHub: suspicious
This appears to be a genuine monitoring and recovery skill, but it can automatically kill sessions, restart services, inspect broad host state, and make external network probes with limited user safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026