SKILLEMALL.ai

BB hypii-hyperliquid-trader

Hypii AI Trading Agent for Hyperliquid perpetual futures. Automated trading strategies with SkillPay micropayment integration. Features: - DCA (Dollar Cost Averaging) Strategy - Grid Trading Strategy - AI Trading Signals - Portfolio Management - Automated Trade Execution Pricing: - 5 free calls per day - 0.01 USDT for basic queries - 0.05 USDT for strategy execution - 0.1 USDT for automated trading - 19.9 USDT/month for unlimited Pro access

ClawHub Agent Skills author: JIAWEI YIN v1.0.0 26 files body ≈ 1 371 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting

IntegrationAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
89
Quality 40%
73
Run on models
none yet
Process rating
B
70/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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 · 11

✓ No critical or high findings

Medium and low: 11
  • low Secrets in code secret-high-entropy-token check-balance.mjs:3
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const address = '0x14…3Ca';
    quoted
  • low Secrets in code secret-high-entropy-token lib/x402.js:37
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    token: '0x83…913', // USDC on Base
    quoted
  • low Secrets in code secret-high-entropy-token package-lock.json:25
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…SHP+Ptfk…NUA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:46
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…jgR+Mkmf+D189…ihQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:73
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:103
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:150
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…FrF+LTRo…W3g==",
    detector
  • low Secrets in code secret-high-entropy-token test-fixed.mjs:13
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    return '0x14…3Ca';
    fixturequoted
  • low Secrets in code secret-high-entropy-token test-x402.mjs:9
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    const billing = new X402Billing('0x14…3Ca');
    fixturequoted
  • low Secrets in code secret-high-entropy-token trade-minvalue.mjs:40
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const balance = await sdk.info.perpetuals.getClearinghouseState('0x14…3Ca');
    quoted
  • low Secrets in code secret-high-entropy-token X402_CONFIG.md:73
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "recipient": "0x14…3Ca",
    quoted

Files scanned: 26. 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 70/100

  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 22 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1371 tokens
  • 100Running it twice. No mutating operations
  • 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)
  • -212 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 446: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 22 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)

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

External checks

ClawHub: suspicious
This crypto trading skill can place live orders and ships exposed trading-key material in runnable scripts, so it needs review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026