SKILLEMALL.ai
GitHub ↗ RU Sign in

CC cognitive-brain-deploy

Cognitive Brain 语义记忆系统一键部署工具。当用户需要部署 OpenClaw 认知脑、部署 PostgreSQL+pgvector 向量数据库、安装 Cognitive Brain Skill、配置定时任务和 Hook 时使用。

Not recommendedcritical or high security findings
ClawHub Agent Skills author: hongjiahao371-pixel v1.0.0 MIT-0 5 files · 1 script body ≈ 230 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ProcedurePostgreSQLInfrastructuretype 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
69/100
safety, quality, tests
Safety 60%
62
Quality 40%
79
Run on models
none yet
Process rating
C
51/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

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.
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 · 13

  • high Dangerous commands cmd-persistence scripts/deploy.sh:172
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null; echo "$CRON_CMD1"; echo "$CRON_CMD2"; echo "$CRON_CMD3") | crontab -
Medium and low: 12
  • medium Dangerous commands cmd-pipe-to-shell-known-host references/deploy-guide.md:19
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -fsSL https://deb.nodesource.com/setup_18.x | sudo bash - && \
  • medium Dangerous commands cmd-pipe-to-shell-known-host references/troubleshooting.md:67
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -fsSL https://deb.nodesource.com/setup_18.x | sudo bash -
  • low Dangerous commands cmd-privilege references/deploy-guide.md:19
    Privilege escalation / world-writable permissions (detector / deny-list definition)
    curl -fsSL https://deb.nodesource.com/setup_18.x | sudo bash - && \
    detector
  • low Dangerous commands cmd-background-process references/deploy-guide.md:21
    Starts a background / autostarted process
    sudo systemctl enable --now postgresql redis
  • low Dangerous commands cmd-cron-mention references/deploy-guide.md:155
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-background-process references/troubleshooting.md:13
    Starts a background / autostarted process
    sudo systemctl enable postgresql
  • low Dangerous commands cmd-background-process references/troubleshooting.md:55
    Starts a background / autostarted process
    sudo systemctl enable redis
  • low Dangerous commands cmd-privilege references/troubleshooting.md:67
    Privilege escalation / world-writable permissions (detector / deny-list definition)
    curl -fsSL https://deb.nodesource.com/setup_18.x | sudo bash -
    detector
  • low Dangerous commands cmd-privilege scripts/deploy.sh:45
    Privilege escalation / world-writable permissions (detector / deny-list definition)
    curl -fsSL https://deb.nodesource.com/setup_18.x | $SUDO bash - || error "Node.js 安装失败"
    detector
  • low Dangerous commands cmd-background-process scripts/deploy.sh:51
    Starts a background / autostarted process
    $SUDO systemctl enable --now postgresql redis
  • low Dangerous commands cmd-cron-mention scripts/deploy.sh:169
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "brain-forget.cjs"; then
  • low Dangerous commands cmd-cron-mention scripts/deploy.sh:172
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "$CRON_CMD1"; echo "$CRON_CMD2"; echo "$CRON_CMD3") | crontab -

Files scanned: 5. 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 51/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
  • 30Running it twice. 4 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 230 tokens

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 121: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This looks like a real deployment helper, but it needs review because it makes privileged system changes and installs persistent memory-related jobs with limited user control.
LLM: suspicious (high) · VirusTotal: · 29 May 2026