AC Hyperliquid Radar
Free Hyperliquid portfolio, funding, and wallet research (read-only): wallet_report, positions, fills, open_orders, funding_snapshot, position_health. Use when the user asks about Hyperliquid portfolio, funding rates/payments, wallet research, positions, fills, margin, or liquidation risk — not for placing trades. No private keys. No paid keys. Install: npx @hypelens/hypelens-radar@0.1.5. Keywords: hyperliquid portfolio funding wallet radar positions fills research mcp read-only.
Free Hyperliquid portfolio, funding, and wallet research (read-only): walletreport, positions, fills, openorders, fundingsnapshot, positionhealth.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "topics"
Process rating: all ten parameters 56/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
- 40Consistency. Frontmatter name (Hyperliquid Radar) differs from the folder (hyperliquid-radar)
- 85Steps. 5 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 341 tokens
- 100Running it twice. No mutating operations
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 484: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.