SKILLEMALL.ai

BF capability-evolver

A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution.

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

As a process F 37/100 · Will not run — References files that are not bundled: assets/gep/events.jsonl

AnalyzerAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
37/100
Will not run
References files that are not bundled: assets/gep/events.jsonl
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
This is a copy of a skill from another catalog; the rating counts the canonical one: capability-evolver (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 · 0

✓ No critical or high findings

Files scanned: 63. 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: assets/gep/events.jsonl

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: assets/gep/events.jsonl
  • 0Tools and files. 1 referenced file(s) missing: assets/gep/events.jsonl
  • 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
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (capability-evolver) differs from the folder (evolver-bak)
  • 70Failures and branches. 4 branches
  • 100Steps. 14 steps
  • 100Execution cost. Instruction body is 1009 tokens
  • 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)
  • +3Output format is not stated: the model decides each time
  • -314 of 14 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 132: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 14 items
  • +4Has examples (6 code blocks)

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

External checks

ClawHub: suspicious
This is a powerful self-evolution tool, but it can read broad agent history, contact external services, claim external tasks, persist identifiers, run updates, and spawn long-running automation with insufficient user-facing control.
LLM: suspicious (high) · VirusTotal: · 29 May 2026