CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hyperliquid

Hyperliquid L1 perps DEX (69% market share)

53

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/hyperliquid/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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, highly actionable command reference with excellent executable examples, but it is a monolithic inline catalog and lacks validation checkpoints for its destructive trading operations.

Suggestions

Add a validation/confirmation step before live trades, e.g. 'Before placing a real order, echo the parsed args and confirm unless DRY_RUN=true; after /hl long, verify with /hl balance.'

Move the bulk command tables into a references/ file (e.g. COMMANDS.md) and keep SKILL.md as a Quick Start overview pointing to it.

Collapse the redundant Examples blocks that restate the Trading table rows to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly lean command tables with copy-paste examples, but examples restate table rows and the Shortcuts table duplicates commands, leaving minor trimmable repetition.

4 / 5

Actionability

Commands are fully executable with concrete argument signatures and worked examples (e.g. '/hl long BTC 0.1 45000 # Limit long at $45,000') covering the common cases.

5 / 5

Workflow Clarity

Quick Start sequences set-credentials -> balance -> open -> close, but for a destructive real-money trading skill there are no validation/confirmation checkpoints, capping this at 3.

3 / 5

Progressive Disclosure

Section headers organize the content well, but ~250 lines of inline command reference with no bundle files or one-level-deep references could be split into separate reference files.

3 / 5

Total

15

/

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 identifies a distinct niche but is thin: it states the category with no concrete actions and no usage trigger, relying on a market-share boast for padding.

Suggestions

Replace the market-share fluff with concrete actions, e.g. 'Trade perpetuals and spot, manage HLP vault deposits, run TWAP orders, and track portfolio PnL on Hyperliquid L1.'

Add an explicit trigger clause: 'Use when the user wants to trade, check balances, or manage positions on Hyperliquid.'

Drop first/second person and keep third person ('Trades ...', 'Manages ...') to maximize specificity.

DimensionReasoningScore

Specificity

The description names the domain ('Hyperliquid L1 perps DEX') but lists no concrete actions, and '(69% market share)' is marketing fluff rather than a capability.

2 / 5

Completeness

It conveys a partial 'what' (a perps DEX) but entirely lacks a 'when' / 'Use when...' clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

'Hyperliquid' and 'perps' are natural terms a user would say, but common variations like 'trading', 'leverage', 'futures', or 'HYPE' are absent.

3 / 5

Distinctiveness Conflict Risk

The brand name 'Hyperliquid' plus 'perps DEX' carves a clear niche with minimal overlap, though no trigger phrase sharpens it further.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/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.