AB hyperliquid
Trade and monitor Hyperliquid perpetual futures. Check balances, view positions with P&L, place/cancel orders, execute market trades. Use when the user asks about Hyperliquid trading, portfolio status, crypto positions, or wants to execute trades on Hyperliquid.
As a process B 74/100 · Nearly there — weak spots: consistency, progress reporting
How to improve
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Exfiltration
read-dotenvREADME.md:63Reads a .env filecp .env.example .env
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:26High-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-tokenscripts/package-lock.json:47High-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-tokenscripts/package-lock.json:74High-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-tokenscripts/package-lock.json:80High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Zif+qXa4n+oYzK…TZQ/vlgJrCoNQlg==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:104High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
detector
Files scanned: 11. 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 74/100
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (hyperliquid) differs from the folder (hyperliquid-trading)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 44 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1139 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
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)
- -34 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 262: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 44 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.