SKILLEMALL.ai
GitHub ↗ RU Sign in

BD hyperclaw

Trade on Hyperliquid. Supports 228+ perps, HIP-3 equity/commodity perps (TSLA, GOLD), market scanning, sentiment analysis, Grok web/X search, and prediction market data. Commands for account status, market data, funding rates, order book, trading, and intelligence gathering.

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

Trade on Hyperliquid.

As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureSoftware developmentAI and agentstype 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
82/100
safety, quality, tests
Safety 60%
88
Quality 40%
73
Run on models
none yet
Process rating
D
45/100
Unfinished process
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

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Risky intent medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.

For the author

Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.

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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Risky intent intent-wallet-secrets SKILL.md:33
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    Get API keys from: https://app.hyperliquid.xyz/API — use a separate API wallet, not your main wallet private key.
  • medium Risky intent intent-wallet-secrets SKILL.md:214
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    | `HL_SECRET_KEY` | For trading | API wallet private key |
  • low Exfiltration read-dotenv README.md:19
    Reads a .env file
    cp hyperclaw/.env.example hyperclaw/.env
  • low Risky intent intent-wallet-secrets scripts/hyperliquid_tools.py:72
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)
    print(f"  HL_SECRET_KEY=0x...       # API wallet private key")
    quoted

Files scanned: 6. 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 45/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
  • 30Running it twice. 4 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 85Steps. 6 steps, 3 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3520 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
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 275: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (9 code blocks)
  • +3All 3 scripts are documented

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