CtrlK
BlogDocsLog inGet started
Tessl Logo

hyperliquid

Hyperliquid market data, account history, trade review.

53

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/blockchain/hyperliquid/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, highly actionable read-only CLI skill with concrete copy-paste commands, a clear multi-step procedure, pitfalls, and verification, with only minor conciseness redundancy and no per-step validation checkpoints.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanations of what Hyperliquid, perpetuals, or funding are) and is dense, but the 12-command surface appears three times (inline list, Quick Reference, Procedure), a minor redundancy that could be tightened.

4 / 5

Actionability

Quick Reference gives full command signatures with all flags and Procedure gives copy-paste-ready worked examples with real arguments (e.g. `candles BTC --interval 1h --hours 72 --limit 48`), and a runnable Verification command, covering the common cases.

5 / 5

Workflow Clarity

The 7-step Procedure is a clearly sequenced workflow with a refinement loop in step 6 (review → fills/orders → candles/funding → judge) and error-recovery guidance in Pitfalls, plus an end Verification checkpoint, but there are no explicit per-step validation checkpoints.

4 / 5

Progressive Disclosure

Clear section headers give easy navigation and the single bundle reference (the script path) is well-signaled and one level deep, but it is a single-file skill with minimal reference structure rather than the multi-file split of the top anchor.

4 / 5

Total

17

/

20

Passed

Description

40%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly anchors on a distinctive platform name and lists three data domains, but it is a terse noun phrase with no action verbs and no "Use when" trigger guidance, leaving both specificity and completeness weak.

Suggestions

Rewrite as action verbs with a trigger clause, e.g. "Query Hyperliquid market data, account history, and post-trade reviews. Use when the user asks for Hyperliquid perp/spot candles, funding, L2 book, positions, fills, or trade reviews."

Add natural trigger synonyms users actually say (perps, perpetuals, spot, candles, funding, order book, L2, fills, PnL) to improve trigger-term coverage.

Make the "what" concrete with verbs (query, inspect, export) rather than noun phrases like "market data, account history".

DimensionReasoningScore

Specificity

The description names the domain ("Hyperliquid") and three data categories ("market data, account history, trade review"), but these are generic noun phrases with no concrete action verbs, matching the anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

A vague, noun-based "what" is present but there is no "Use when..." trigger guidance at all, fitting the anchor for a vague "what" with no "when"; the missing trigger clause also caps this dimension.

2 / 5

Trigger Term Quality

"Hyperliquid" is a strong, specific trigger term and the three data categories are relevant, but common natural variations users say (perps, candles, funding, order book, L2, fills, PnL) are absent, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The platform name "Hyperliquid" carves a clear niche with low conflict risk, but the generic data terms ("market data", "account history", "trade review") leave minor overlap risk with other crypto/trading skills.

4 / 5

Total

11

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.