CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hyperliquid

Hyperliquid market data, account history, trade review.

59

Quality

74%

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

92%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 strong example of a CLI-wrapper skill: fully executable commands with real example arguments that match the actual bundled script, a clearly sequenced procedure with error-recovery guidance and a verification step, and appropriate separation of usage documentation from the implementation script. The only notable weakness is token-level repetition of the invocation path and dual command listings (Quick Reference plus Procedure).

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no padding about what Hyperliquid, funding, or order books are — and every section carries skill-specific information (commands, flags, endpoint quirks, pitfalls). It misses a 5 because the full `~/.hermes/skills/...` invocation path is repeated in every Procedure example and all 12 command syntaxes appear in both Quick Reference and Procedure.

4 / 5

Actionability

Every command is fully executable and copy-paste ready with flags, defaults, and concrete example arguments (`candles BTC --interval 1h --hours 72`, `export BTC --end-time-ms 1760000000000`, `review --coin BTC --hours 168`), and all 12 subcommands and flags were verified to exist in `scripts/hyperliquid_client.py`. The Verification section adds a runnable check with expected output.

5 / 5

Workflow Clarity

The Procedure is clearly sequenced (discover dexs/markets, pull history, inspect live book, review account, fills, trade review, export), step 6 chains an explicit deeper-analysis flow (review → fills/orders → candles/funding), and the Pitfalls section provides error-recovery feedback ("iterate with later `startTime` values" for rate-limited/capped windows). A final Verification step with expected output completes the loop; the skill is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

The bundle is appropriately split: the 60KB implementation lives in `scripts/hyperliquid_client.py` (the referenced helper path matches the bundle file), while SKILL.md stays at overview/usage level with well-organized sections (When to Use, Prerequisites, Quick Reference, Procedure, Pitfalls, Verification) and no nested references. Navigation is easy and the single script reference is clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

48%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 is terse and anchored by the distinctive "Hyperliquid" name, giving it a clear niche, but it is a bare domain list with no action verbs, no "Use when..." trigger clause, and no keyword coverage of the skill's main capabilities (candles, funding, order books, positions, fills). It communicates what data is covered but not what the skill does with it or when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Hyperliquid markets, candles, funding rates, order books, or a wallet's positions, balances, fills, or orders."

Add action verbs and command-level keywords so the "what" covers concrete capabilities: fetch candles and funding history, inspect the L2 order book, review wallet positions and fills, export normalized datasets.

State the read-only/public-data boundary (no order placement) to sharpen the "what" and distinguish this skill from trade-execution skills.

DimensionReasoningScore

Specificity

The description names three specific areas ("Hyperliquid market data, account history, trade review") but contains no action verbs, matching the anchor for naming the domain with minimal or generic actions. It falls below anchor 3 because no concrete actions (query, fetch, export, review) are explicitly stated.

2 / 5

Completeness

The "what" is reasonably clear (three Hyperliquid data areas), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not a 4 because the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

"Hyperliquid" is a strong natural trigger term and "market data" and "trade review" are phrases users would say, but common natural terms for the skill's capabilities (candles, funding, order book, positions, balances, fills) are missing. This matches the anchor for some relevant keywords missing common variations, not anchor 4 since more than a few natural terms are absent.

3 / 5

Distinctiveness Conflict Risk

The distinctive platform name "Hyperliquid" anchors triggers and minimizes wrong-skill conflicts, but the generic trailing phrases "market data", "account history", and "trade review" overlap with other crypto/trading-analysis skills. This matches the anchor for mostly distinct with minor overlap risk, not 5 because those generic terms could trigger sibling trading skills.

4 / 5

Total

12

/

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.

Validation — 13 / 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

Path

optional-skills/blockchain/hyperliquid/SKILL.md

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.