SKILLEMALL.ai
GitHub ↗ RU Sign in

CF BABY Brain - Ultimate AI Assistant Platform

<p align="center"> <img src="https://img.shields.io/badge/Version-1.0.0-blue" alt="Version"> <img src="https://img.shields.io/badge/Author-Baby-orange" alt="Author"> <img src="https://img.shields.i...

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 11 files · 7 scripts body ≈ 4 087 tokens Open the sourcegithub.com↗ analyzed 2 d ago

<p align="center"> <img src="https://img.shields.io/badge/Version-1.0.0-blue" alt="Version"> <img src="https://img.shields.io/badge/Author-Baby-orange"…

As a process F 34/100 · Will not run — References files that are not bundled: docs/getting-started.md, docs/commands.md, docs/api.md

ProcedureDiscordWhatsAppGitHubSoftware developmentData and analyticsInfrastructuretype 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
C
64/100
safety, quality, tests
Safety 60%
64
Quality 40%
65
Run on models
none yet
Process rating
F
34/100
Will not run
References files that are not bundled: docs/getting-started.md, docs/commands.md, docs/api.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. 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 · 11

  • high Dangerous commands cmd-persistence scripts/automation.sh:400
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null || true; echo "$cron_entry") | crontab -
Medium and low: 10
  • medium Dangerous commands cmd-persistence references/tools.md:467
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)
    echo "0 2 * * * /path/to/command" | crontab -
    security skill
  • medium Dangerous commands cmd-persistence scripts/automation.sh:349
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    crontab -l 2>/dev/null | grep -v "$remove" | crontab -
    detector
  • low Dangerous commands cmd-cron-mention references/tools.md:461
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -l
    security skill
  • low Dangerous commands cmd-cron-mention references/tools.md:464
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -e
    security skill
  • low Dangerous commands cmd-cron-mention scripts/automation.sh:339
    Mentions editing / listing crontab
    crontab -l 2>/dev/null | grep -i "baby-brain" || echo "No BABY Brain tasks scheduled"
  • low Dangerous commands cmd-cron-mention scripts/automation.sh:349
    Mentions editing / listing crontab
    crontab -l 2>/dev/null | grep -v "$remove" | crontab -
  • low Dangerous commands cmd-cron-mention scripts/automation.sh:400
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null || true; echo "$cron_entry") | crontab -
  • low Risky intent intent-offensive-security SKILL.md:78
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ### 🔐 Security & Penetration Testing
  • low Risky intent intent-offensive-security SKILL.md:489
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
    > **"The security module alone is worth 100x the install. Full pentesting suite built-in."**
    quoted
  • low Risky intent intent-offensive-security SKILL.md:564
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration testing

Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: docs/getting-started.md
  • warning missing-ref reference to a missing file: docs/commands.md
  • warning missing-ref reference to a missing file: docs/api.md
  • warning missing-ref reference to a missing file: docs/security.md
  • warning missing-ref reference to a missing file: LICENSE

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: docs/getting-started.md, docs/commands.md, docs/api.md
  • 0Tools and files. 5 referenced file(s) missing: docs/getting-started.md, docs/commands.md, docs/api.md
  • 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. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (BABY Brain - Ultimate AI Assistant Platform) differs from the folder (baby-brain)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4087 tokens
  • 100Steps. 85 steps
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 17 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -288 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 57 headings
  • +3Step-by-step instructions: 85 items
  • +4Has examples (22 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 7 scripts are documented

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