SKILLEMALL.ai

DB hummingbot-deploy

Deploy Hummingbot trading infrastructure including API server, MCP server, and Condor Telegram bot. Use this skill when the user wants to install, deploy, set up, or configure Hummingbot.

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files · 3 scripts body ≈ 1 332 tokens Open the sourcegithub.com analyzed 2 d ago

Deploy Hummingbot trading infrastructure including API server, MCP server, and Condor Telegram bot.

As a process B 70/100 · Nearly there — weak spots: result and completion

IntegrationTelegramGitHubDockerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
52/100
safety, quality, tests
Safety 60%
28
Quality 40%
87
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
0
Tools and files w 18
60
When it triggers w 12
70
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.
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 · 4

  • high Dangerous commands cmd-pipe-to-shell SKILL.md:35
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    bash <(curl -s https://raw.githubusercontent.com/hummingbot/skills/main/skills/hummingbot-deploy/scripts/check_env.sh)
  • high Dangerous commands cmd-pipe-to-shell SKILL.md:106
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    bash <(curl -s https://raw.githubusercontent.com/hummingbot/skills/main/skills/hummingbot-deploy/scripts/install_mcp.sh) \
  • high Dangerous commands cmd-pipe-to-shell SKILL.md:112
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    bash <(curl -s https://raw.githubusercontent.com/hummingbot/skills/main/skills/hummingbot-deploy/scripts/install_mcp.sh) \
  • high Dangerous commands cmd-pipe-to-shell SKILL.md:144
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    bash <(curl -s https://raw.githubusercontent.com/hummingbot/skills/main/skills/hummingbot-deploy/scripts/verify.sh)

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 70/100

  • 0Result and completion. Does not say what the result is
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 10 steps, 2 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1332 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 187: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (13 code blocks)
  • +3All 3 scripts are documented

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