SKILLEMALL.ai
GitHub ↗ RU Sign in

BC autonomous-brain

Advanced autonomous AI brain with proactive monitoring, intelligent decision-making, context awareness, and seamless task execution. Enables OpenClaw to think independently, anticipate needs, and act without constant user direction.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 1 609 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Advanced autonomous AI brain with proactive monitoring, intelligent decision-making, context awareness, and seamless task execution.

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

GeneratorInfrastructureSoftware developmenttype 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
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
68
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
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 Risky intent intent-offensive-security SKILL.md:179
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **kali-pentest** - Security operations

Files scanned: 3. 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 58/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 108 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1609 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 232: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 108 items

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